{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80563 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80563 is an use after free vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80563 and fix it if it is affected.\n\nWhat it is: CVE-2026-80563 is an use after free vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80563 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80563/ (Markdown: https://insights.sbomify.com/CVE-2026-80563/index.md)","id":"CVE-2026-80563","markdown":"https://insights.sbomify.com/CVE-2026-80563/index.md","name":"CVE-2026-80563","record":{"aliases":["BELL-CVE-2026-80563","DEBIAN-CVE-2026-80563","UBUNTU-CVE-2026-80563"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with root privileges can trigger a use-after-free in the Linux kernel GPIO driver via debugfs, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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(\u0026priv-\u003eblob_lock)\n                                     debugfs_remove_recursive()  [no wait]\n                                     mutex_unlock(\u0026priv-\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind","id":"CVE-2026-80563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"gve: fix NULL dereference due to missing ptp adjfine","id":"CVE-2026-80564"},"packages":[],"prev":{"headline":"gpio: ml-ioh: use raw_spinlock_t for the register lock","id":"CVE-2026-80562"},"products":["Linux"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-26","vendors":["Linux"]},"summary":"A local attacker with root privileges can trigger a use-after-free in the Linux kernel GPIO driver via debugfs, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-80563/"}