VulnerabilityPublished 13 Jan 2026Updated 10 Nov 2026

CVE-2025-68814: Linux kernel · io_uring: fix filename leak in __io_openat_prep()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e232269d511566b1f80872256a48593acc1becf4 : update Linux kernel when convenient.

Data as of 10 Nov 2026, 13:18 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Patch: Available – fixed in e232269d511566b1f80872256a48593acc1becf4, b14fad555302a2104948feaff70503b64c80ac01, 2420ef01b2e836fbc05a0a8c73a1016504eb0458 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < e232269d511566b1f80872256a48593acc1becf4	Fixed in e232269d511566b1f80872256a48593acc1becf4
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < b14fad555302a2104948feaff70503b64c80ac01	Fixed in b14fad555302a2104948feaff70503b64c80ac01
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < 2420ef01b2e836fbc05a0a8c73a1016504eb0458	Fixed in 2420ef01b2e836fbc05a0a8c73a1016504eb0458
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < 18b99fa603d0df5e1c898699c17d3b92ddc80746	Fixed in 18b99fa603d0df5e1c898699c17d3b92ddc80746
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < 8f44c4a550570cd5903625133f938c6b51310c9b	Fixed in 8f44c4a550570cd5903625133f938c6b51310c9b
LinuxLinux	Affected ≥ b9445598d8c60a1379887b957024b71343965f74, < 7fbfb85b05bc960cc50e09d03e5e562131e48d45	Fixed in 7fbfb85b05bc960cc50e09d03e5e562131e48d45

AI-suggested

A fix is available and has been applied in the Linux kernel commits identified by hashes e232269d511566b1f80872256a48593acc1becf4, b14fad555302a2104948feaff70503b64c80ac01, 2420ef01b2e836fbc05a0a8c73a1016504eb0458, 18b99fa603d0df5e1c898699c17d3b92ddc80746, 8f44c4a550570cd5903625133f938c6b51310c9b, and 7fbfb85b05bc960cc50e09d03e5e562131e48d45. Users and administrators should update to a patched kernel version to remediate this issue.

Description

A memory leak vulnerability was identified and fixed in the Linux kernel's io_uring subsystem within the __io_openat_prep() function. The issue occurs when a filename structure allocated by getname() is not properly cleaned up due to an early return condition combined with the O_CLOEXEC flag, leading to leaked memory. The fix involves setting a cleanup flag to ensure the allocated memory is freed when the request is torn down.

Impact

The vulnerability causes a memory leak in the kernel when certain file open operations occur with specific flags. While it does not directly lead to code execution or privilege escalation, memory leaks can degrade system stability and potentially be leveraged in denial-of-service scenarios if exploited at scale.

Summary

CVE-2025-68814 addresses a memory leak in the Linux kernel's io_uring implementation. Specifically, in the __io_openat_prep() function, a struct filename is allocated via getname(). Under conditions where the file is installed in the fixed file table and the O_CLOEXEC flag is set, the function returns early without setting the REQ_F_NEED_CLEANUP flag. This omission prevents the allocated filename memory from being freed, causing a leak. The patch sets the REQ_F_NEED_CLEANUP flag immediately after the successful getname() call to guarantee proper cleanup of the filename and other resources.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 13:18 UTC

Technical details

References

Community reviews

Related threats