gpio: sysfs: fix chip removal with GPIOs exported over sysfs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a645cc25904b0baf508b77a0402ce151212b9800, Kernel 6.19.6, Kernel 6766f59012301f1bf3f46c6e7149caca45d92309 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: gpio: sysfs: fix chip removal with GPIOs exported over sysfs Currently if we export a GPIO over sysfs and unbind the parent GPIO controller, the exported attribute will remain under /sys/class/gpio because once we remove the parent device, we can no longer associate the descriptor with it in gpiod_unexport() and never drop the final reference. Rework the teardown code: provide an unlocked variant of gpiod_unexport() and remove all exported GPIOs with the sysfs_lock taken before unregistering the parent device itself. This is done to prevent any new exports happening before we unregister the device completely.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1cd53df733c21ae0d344a2dec941a3e2a06fefd9 <a645cc25904b0baf508b77a0402ce151212b9800, >=6.19 <6.19.6, >=1cd53df733c21ae0d344a2dec941a3e2a06fefd9 <6766f59012301f1bf3f46c6e7149caca45d92309, >=6.17 <6.18.16, =6.17, >=1cd53df733c21ae0d344a2dec941a3e2a06fefd9 <54f463494eb5bf193ef7d904a493474c451734df | a645cc25904b0baf508b77a0402ce151212b9800, 6.19.6, 6766f59012301f1bf3f46c6e7149caca45d92309, 6.18.16, 54f463494eb5bf193ef7d904a493474c451734df |
| linux-kernel: Kernel | >=6.17.0 <6.18.16, >=6.19.0 <6.19.6 | 6.18.16, 6.19.6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket