gpio: cdev: make sure the cdev fd is still active before emitting events
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d4cd0902c156b2ca60fdda8cd8b5bcb4b0e9ed64 and Kernel dccc6daa8afa0f64c432e4c867f275747e3415e1.
In the Linux kernel, the following vulnerability has been resolved: gpio: cdev: make sure the cdev fd is still active before emitting events With the final call to fput() on a file descriptor, the release action may be deferred and scheduled on a work queue. The reference count of that descriptor is still zero and it must not be used. It's possible that a GPIO change, we want to notify the user-space about, happens AFTER the reference count on the file descriptor associated with the character device went down to zero but BEFORE the .release() callback was called from the workqueue and so BEFORE we unregistered from the notifier. Using the regular get_file() routine in this situation triggers the following warning: struct file::f_count incremented from zero; use-after-free condition present! So use the get_file_active() variant that will return NULL on file descriptors that have been or are being released.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.13, >=40b7c49950bd56c984b1f6722f865b922879260e <d4cd0902c156b2ca60fdda8cd8b5bcb4b0e9ed64, >=40b7c49950bd56c984b1f6722f865b922879260e <dccc6daa8afa0f64c432e4c867f275747e3415e1 | d4cd0902c156b2ca60fdda8cd8b5bcb4b0e9ed64, dccc6daa8afa0f64c432e4c867f275747e3415e1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket