{"id":"CVE-2026-80563","summary":"gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind\n\nThe \"trigger\" debugfs file has a hand-rolled -\u003ewrite handler\n(trigger_write()) that dereferences the per-device gpio_la_poll_priv. The\nfile is created with debugfs_create_file_unsafe(), and the handler never\ntakes a debugfs reference. Nothing keeps the object alive while the\nhandler runs.\n\npriv is allocated with devm_kzalloc(). devres frees it when the platform\ndevice is unbound. debugfs_create_file_unsafe() installs no full_proxy\nwrapper, so debugfs_remove_recursive() in gpio_la_poll_remove() does not\nwait for an in-flight trigger_write(). The blob_lock taken there does not\nhelp, because trigger_write() never takes it. A write that races an unbind\ntherefore writes into freed memory:\n\n  trigger_write()                  gpio_la_poll_remove()\n    priv = m-\u003eprivate\n    buf = memdup_user()  [may sleep]\n                                     mutex_lock(&priv-\u003eblob_lock)\n                                     debugfs_remove_recursive()  [no wait]\n                                     mutex_unlock(&priv-\u003eblob_lock)\n                                   (remove returns; devres frees priv)\n    priv-\u003etrig_data = buf   \u003c-- use-after-free write\n    priv-\u003etrig_len  = count\n\nThe race is reachable by root via\n/sys/bus/platform/drivers/gpio-sloppy-logic-analyzer/unbind.\n\nCreate \"trigger\" with debugfs_create_file() instead. Its full_proxy\nwrapper makes debugfs_remove_recursive() drain any in-flight -\u003ewrite\nbefore it returns.\n\nThe use-after-free is confirmed under KASAN with a minimal reproducer of\nthe same debugfs_create_file_unsafe() plus devm_kzalloc() pattern\n(available on request); it produces a slab-use-after-free write in the\nhandler.","modified":"2026-08-28T11:48:23.514763232Z","published":"2026-08-26T14:37:27.759Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80563.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/23e9f32c0c7d2043e39655cff5ee3ddf29a43f80"},{"type":"WEB","url":"https://git.kernel.org/stable/c/24bef4918f6ab806260476e2f93d8f791fd17449"},{"type":"WEB","url":"https://git.kernel.org/stable/c/44f3468a0aef1aabdad551898ab7cfa2a9d20e99"},{"type":"WEB","url":"https://git.kernel.org/stable/c/49a1ebb1ef2c8ada300c174b65273810abb4e326"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80563.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80563"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"7828b7bbbf2074dd7dd14d87f50bc5ce9036d692"},{"fixed":"49a1ebb1ef2c8ada300c174b65273810abb4e326"},{"fixed":"23e9f32c0c7d2043e39655cff5ee3ddf29a43f80"},{"fixed":"24bef4918f6ab806260476e2f93d8f791fd17449"},{"fixed":"44f3468a0aef1aabdad551898ab7cfa2a9d20e99"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80563.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.11.0"},{"fixed":"6.12.105"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.46"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.10"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80563.json"}}],"schema_version":"1.9.0"}