Local service interruption via io_uring filename leak
Published Jan 13, 2026 · Updated Jan 13, 2026
Memory leak in the io_uring open path in Linux Kernel allows local users to interrupt service through crafted asynchronous open requests. The __io_openat_prep() function allocates a struct filename with getname(), then returns early for fixed-file installation with O_CLOEXEC before setting REQ_F_NEED_CLEANUP, so request teardown does not release the allocation. Local users able to submit repeated io_uring open requests can consume kernel memory and degrade or interrupt the host, without a reported confidentiality or integrity impact.
Summary
What happened
Memory leak in the io_uring open path in Linux Kernel allows local users to interrupt service through crafted asynchronous open requests. The __io_openat_prep() function allocates a struct filename with getname(), then returns early for fixed-file installation with O_CLOEXEC before setting REQ_F_NEED_CLEANUP, so request teardown does not release the allocation. Local users able to submit repeated io_uring open requests can consume kernel memory and degrade or interrupt the host, without a reported confidentiality or integrity impact.
The record
- CVE
- CVE-2025-68814
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.15
- Affected versionversion=b9445598d8c60a1379887b957024b71343965f74 <18b99fa603d0df5e1c898699c17d3b92ddc80746
- Affected versionversion=b9445598d8c60a1379887b957024b71343965f74 <7fbfb85b05bc960cc50e09d03e5e562131e48d45
- Affected versionversion=b9445598d8c60a1379887b957024b71343965f74 <8f44c4a550570cd5903625133f938c6b51310c9b
- Affected versionversion=b9445598d8c60a1379887b957024b71343965f74 <b14fad555302a2104948feaff70503b64c80ac01
- Affected versionversion=b9445598d8c60a1379887b957024b71343965f74 <e232269d511566b1f80872256a48593acc1becf4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo