CVE-2026-93054 | 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 th
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().
- 🔗 git.kernel.org/stable/c/63eaa7663335d482a8825c231213e312…
- 🔗 git.kernel.org/stable/c/df4faf65194ec6c315a59be4c6749eae…
- 🔗 git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee0…
- 🔗 git.kernel.org/stable/c/15340b00e665af805523b08515294a1a…
- 🔗 git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c7…
- 🔗 git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01…
- 🔗 git.kernel.org/stable/c/ec5bd6731183eb6f619140c9bef2ee11…
- 🔗 git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a…
Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | 2026-09-02 | 2026-09-20 |
|---|---|---|
| ≥90 % | 0 | 489 |
| ≥50 % | 0 | 1477 |
| ≥10 % | 0 | 0 |
| <10 % | 300 | 0 |
CVE-2026-93054 | 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 th
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 fail