# CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep()

> A local attacker can trigger a memory leak in the Linux kernel io_uring subsystem, potentially leading to resource exhaustion and denial of service.

- **Severity:** Not scored
- **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:** 13 Jan 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-74381, BELL-CVE-2025-68814, DEBIAN-CVE-2025-68814, GHSA-x459-m5f6-mv8q, ROOT-OS-DEBIAN-12-CVE-2025-68814, ROOT-OS-DEBIAN-13-CVE-2025-68814, ROOT-OS-UBUNTU-2204-CVE-2025-68814, ROOT-OS-UBUNTU-2404-CVE-2025-68814, UBUNTU-CVE-2025-68814

## What is CVE-2025-68814?

CVE-2025-68814 is a memory corruption vulnerability in Linux, published on 13 Jan 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:

io_uring: fix filename leak in __io_openat_prep()

 __io_openat_prep() allocates a struct filename using getname(). However,
for the condition of the file being installed in the fixed file table as
well as having O_CLOEXEC flag set, the function returns early. At that
point, the request doesn't have REQ_F_NEED_CLEANUP flag set. Due to this,
the memory for the newly allocated struct filename is not cleaned up,
causing a memory leak.

Fix this by setting the REQ_F_NEED_CLEANUP for the request just after the
successful getname() call, so that when the request is torn down, the
filename will be cleaned up, along with other resources needing cleanup.

## Which versions are affected by CVE-2025-68814?


## How do I fix CVE-2025-68814?

Apply the vendor's patch.

## Is CVE-2025-68814 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68814 and fix it if it is affected.

What it is: CVE-2025-68814 is a memory corruption vulnerability in Linux, published on 13 Jan 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-2025-68814 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-2025-68814/ (Markdown: https://insights.sbomify.com/CVE-2025-68814/index.md)
```

## Sources

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

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