Answer in brief
CVE-2025-68814 records a Unknown severity vulnerability in io_uring: fix filename leak in __io_openat_prep(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-68814 records a Unknown severity vulnerability in io_uring: fix filename leak in __io_openat_prep(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b9445598d8c60a1379887b957024b71343965f74 <2420ef01b2e836fbc05a0a8c73a1016504eb0458 || >=b9445598d8c60a1379887b957024b71343965f74 <8f44c4a550570cd5903625133f938c6b51310c9b || >=b9445598d8c60a1379887b957024b71343965f74 <18b99fa603d0df5e1c898699c17d3b92ddc80746 || >=b9445598d8c60a1379887b957024b71343965f74 <e232269d511566b1f80872256a48593acc1becf4 || >=b9445598d8c60a1379887b957024b71343965f74 <7fbfb85b05bc960cc50e09d03e5e562131e48d45 || >=b9445598d8c60a1379887b957024b71343965f74 <b14fad555302a2104948feaff70503b64c80ac01 | 2420ef01b2e836fbc05a0a8c73a1016504eb0458, 8f44c4a550570cd5903625133f938c6b51310c9b, 18b99fa603d0df5e1c898699c17d3b92ddc80746, e232269d511566b1f80872256a48593acc1becf4, 7fbfb85b05bc960cc50e09d03e5e562131e48d45, b14fad555302a2104948feaff70503b64c80ac01 |
| Linux/Linuxgeneric | 5.15 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Jan 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b9445598d8c60a1379887b957024b71343965f74 <2420ef01b2e836fbc05a0a8c73a1016504eb0458 || >=b9445598d8c60a1379887b957024b71343965f74 <8f44c4a550570cd5903625133f938c6b51310c9b || >=b9445598d8c60a1379887b957024b71343965f74 <18b99fa603d0df5e1c898699c17d3b92ddc80746 || >=b9445598d8c60a1379887b957024b71343965f74 <e232269d511566b1f80872256a48593acc1becf4 || >=b9445598d8c60a1379887b957024b71343965f74 <7fbfb85b05bc960cc50e09d03e5e562131e48d45 || >=b9445598d8c60a1379887b957024b71343965f74 <b14fad555302a2104948feaff70503b64c80ac01 | 2420ef01b2e836fbc05a0a8c73a1016504eb0458, 8f44c4a550570cd5903625133f938c6b51310c9b, 18b99fa603d0df5e1c898699c17d3b92ddc80746, e232269d511566b1f80872256a48593acc1becf4, 7fbfb85b05bc960cc50e09d03e5e562131e48d45, b14fad555302a2104948feaff70503b64c80ac01 |
| Linux/Linuxgeneric | 5.15 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Jan 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.