uio: Fix stale info pointer in failed registration path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ec5bd6731183eb6f619140c9bef2ee11ed818c20, Kernel 4.15, Kernel 15340b00e665af805523b08515294a1aa1778151 and 13 more.
In the Linux kernel, the following vulnerability has been resolved: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the device but leaves idev->info pointing at the caller-owned struct uio_info. That is unsafe when an opener races with the failed registration path. The open file keeps a reference to the uio_device, while the caller sees registration failure and may free its struct uio_info. Later file operations can then follow idev->info and dereference freed memory. Handle post-device_add() failures like unregister: remove UIO attributes while the info pointer is still valid, then clear idev->info under info_lock and wake existing waiters/async users before removing the device and minor. This makes already-open file descriptors observe the same "device gone" state as normal uio_unregister_device().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=a93e7b331568227500186a465fee3c2cb5dffd1f <ec5bd6731183eb6f619140c9bef2ee11ed818c20, >=4.14.100 <4.15, >=a93e7b331568227500186a465fee3c2cb5dffd1f <15340b00e665af805523b08515294a1aa1778151, >=a93e7b331568227500186a465fee3c2cb5dffd1f <16695e9059d80ea6661e8399064b0c01f641dd8c, >=a93e7b331568227500186a465fee3c2cb5dffd1f <234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac, >=a93e7b331568227500186a465fee3c2cb5dffd1f <506b43dde5f9ac0068b1360e6b5dbee07fda59fb, >=a93e7b331568227500186a465fee3c2cb5dffd1f <63eaa7663335d482a8825c231213e312cacea567, >=a93e7b331568227500186a465fee3c2cb5dffd1f <67b6fc084b034a91c3ec7907a3fed89a2450f30b, >=a93e7b331568227500186a465fee3c2cb5dffd1f <df4faf65194ec6c315a59be4c6749eaeb3009243, =085d735c858934e5d5bfaedb1fc98bd9135e6ff1, =4.18 | ec5bd6731183eb6f619140c9bef2ee11ed818c20, 4.15, 15340b00e665af805523b08515294a1aa1778151, 16695e9059d80ea6661e8399064b0c01f641dd8c, 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac, 506b43dde5f9ac0068b1360e6b5dbee07fda59fb, 63eaa7663335d482a8825c231213e312cacea567, 67b6fc084b034a91c3ec7907a3fed89a2450f30b, df4faf65194ec6c315a59be4c6749eaeb3009243 |
| linux-kernel: Kernel | >=4.18.0 <5.10.270, >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=4.14.100 <4.15 | 5.10.270, 5.15.221, 6.1.188, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 4.15 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket