Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-80563— gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Linux 内核中,以下漏洞已得到修复: gpio: sloppy-logic-analyzer:修复解绑时通过 debugfs 触发的 use-after-free(释放后使用)问题 “trigger” debugfs 文件使用了一个手写的 处理函数( ),该函数会解引用每个设备的 。该文件通过 创建,而处理函数从未获取 debugfs 引用。因此,在处理函数执行期间,没有任何机制保证对象保持存活。 是通过 分配的。当平台设备解绑时,devres 会释放该对象。由于 未安装 封装, 中的 不会等待正在进行的

AI Predicted 7.8 Difficulty: Moderate

Affected Version Matrix 10

VendorProduct Version RangeStatus
Linux Linux 7828b7bbbf2074dd7dd14d87f50bc5ce9036d692< 49a1ebb1ef2c8ada300c174b65273810abb4e326 affected
7828b7bbbf2074dd7dd14d87f50bc5ce9036d692< 23e9f32c0c7d2043e39655cff5ee3ddf29a43f80 affected
7828b7bbbf2074dd7dd14d87f50bc5ce9036d692< 24bef4918f6ab806260476e2f93d8f791fd17449 affected
7828b7bbbf2074dd7dd14d87f50bc5ce9036d692< 44f3468a0aef1aabdad551898ab7cfa2a9d20e99 affected
6.11 affected
< 6.11 unaffected
6.12.105≤ 6.12.* unaffected
6.18.46≤ 6.18.* unaffected
… +2 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-80563

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 7828b7bbbf2074dd7dd14d87f50bc5ce9036d692 ~ 49a1ebb1ef2c8ada300c174b65273810abb4e326 -
Linux Linux 6.11 -

II. Public POCs for CVE-2026-80563

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-80563

登录查看更多情报信息。

Patches & Fixes for CVE-2026-80563 (4)

Same Patch Batch · Linux · 2026-08-26 · 92 CVEs total

CVE-2026-80557 libceph: fix OOB read in decode_watchers() via missing bounds check
CVE-2026-80553 s390/vfio_ccw: Cancel existing workqueues
CVE-2026-80552 s390/vfio_ccw: Ensure index for read/write regions are within range
CVE-2026-80549 s390/vfio_ccw: Move cp cleanup out of not operational
CVE-2026-80546 s390/zcrypt: Improve CCA CPRB length and overflow checks
CVE-2026-80547 s390/vfio_ccw: Implement a crw lock
CVE-2026-80545 s390/zcrypt: Improve EP11 CPRB length and overflow checks
CVE-2026-80543 s390/zcrypt: Pad trailing CCA or EP11 message with zeros
CVE-2026-80548 s390/vfio_ccw: Selectively expand io_mutex
CVE-2026-80555 s390/vfio_ccw: Free all memory if cp_init() fails
CVE-2026-80554 s390/vfio_ccw: Limit the number of channel program segments
CVE-2026-80556 mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition
CVE-2026-80559 Input: sur40 - fix input device registration ordering
CVE-2026-80558 libceph: Avoid using invalid osd indices from primary_temp
CVE-2026-80560 openrisc: signal: do not restore privileged SR bits on sigreturn
CVE-2026-80561 libceph: fix multiple unsafe decodes in decode_locker()
CVE-2026-80562 gpio: ml-ioh: use raw_spinlock_t for the register lock
CVE-2026-80564 gve: fix NULL dereference due to missing ptp adjfine
CVE-2026-80565 crypto: qce - fix error path in devm_qce_register_algs
CVE-2026-80566 Input: hynitron_cstxxx - validate touch count and finger IDs

Showing top 20 of 92 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-80563

No comments yet


Leave a comment