Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 20 days later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b9445598d8c60a1379887b957024b71343965f74 – < 2420ef01b2e836fbc05a0a8c73a1016504eb0458
    • affected b9445598d8c60a1379887b957024b71343965f74 – < 8f44c4a550570cd5903625133f938c6b51310c9b
    • affected b9445598d8c60a1379887b957024b71343965f74 – < 18b99fa603d0df5e1c898699c17d3b92ddc80746
    • affected b9445598d8c60a1379887b957024b71343965f74 – < e232269d511566b1f80872256a48593acc1becf4
    • affected b9445598d8c60a1379887b957024b71343965f74 – < 7fbfb85b05bc960cc50e09d03e5e562131e48d45
    • affected b9445598d8c60a1379887b957024b71343965f74 – < b14fad555302a2104948feaff70503b64c80ac01
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68814 badge
[![CVE-2025-68814](https://cveledger.app/badge/CVE-2025-68814.svg)](https://cveledger.app/cve/CVE-2025-68814)

Record last updated .