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

> A race condition in the Linux kernel UIO driver allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102587, BELL-CVE-2026-93054, DEBIAN-CVE-2026-93054, GHSA-v69r-w76r-qv39, UBUNTU-CVE-2026-93054

## What is CVE-2026-93054?

CVE-2026-93054 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93054?


## How do I fix CVE-2026-93054?

Apply the vendor's patch.

## Is CVE-2026-93054 being exploited?

There is no known exploitation of CVE-2026-93054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93054 and fix it if it is affected.

What it is: CVE-2026-93054 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93054 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93054/ (Markdown: https://insights.sbomify.com/CVE-2026-93054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93054
- OSV: https://osv.dev/vulnerability/CVE-2026-93054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93054/
Summaries are generated and may contain mistakes; the official description above is the record.