Answer in brief
CVE-2026-80563 records a Unknown severity vulnerability in gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7828b7bbbf2074dd7dd14d87f50bc5ce9036d692 <49a1ebb1ef2c8ada300c174b65273810abb4e326 || >=7828b7bbbf2074dd7dd14d87f50bc5ce9036d692 <23e9f32c0c7d2043e39655cff5ee3ddf29a43f80 || >=7828b7bbbf2074dd7dd14d87f50bc5ce9036d692 <24bef4918f6ab806260476e2f93d8f791fd17449 || >=7828b7bbbf2074dd7dd14d87f50bc5ce9036d692 <44f3468a0aef1aabdad551898ab7cfa2a9d20e99 | 49a1ebb1ef2c8ada300c174b65273810abb4e326, 23e9f32c0c7d2043e39655cff5ee3ddf29a43f80, 24bef4918f6ab806260476e2f93d8f791fd17449, 44f3468a0aef1aabdad551898ab7cfa2a9d20e99 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 26, 2026
In the Linux kernel, the following vulnerability has been resolved: gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind The "trigger" debugfs file has a hand-rolled ->write handler (trigger_write()) that dereferences the per-device gpio_la_poll_priv. The file is created with debugfs_create_file_unsafe(), and the handler never takes a debugfs reference. Nothing keeps the object alive while the handler runs. priv is allocated with devm_kzalloc(). devres frees it when the platform device is unbound. debugfs_create_file_unsafe() installs no full_proxy wrapper, so debugfs_remove_recursive() in gpio_la_poll_remove() does not wait for an in-flight trigger_write(). The blob_lock taken there does not help, because trigger_write() never takes it. A write that races an unbind therefore writes into freed memory: trigger_write() gpio_la_poll_remove() priv = m->private buf = memdup_user() [may sleep] mutex_lock(&priv->blob_lock) debugfs_remove_recursive() [no wait] mutex_unlock(&priv->blob_lock) (remove returns; devres frees priv) priv->trig_data = buf <-- use-after-free write priv->trig_len = count The race is reachable by root via /sys/bus/platform/drivers/gpio-sloppy-logic-analyzer/unbind. Create "trigger" with debugfs_create_file() instead. Its full_proxy wrapper makes debugfs_remove_recursive() drain any in-flight ->write before it returns. The use-after-free is confirmed under KASAN with a minimal reproducer of the same debugfs_create_file_unsafe() plus devm_kzalloc() pattern (available on request); it produces a slab-use-after-free write in the handler.
Quoted source text, attributed separately from HOL analysis.