Answer in brief
CVE-2025-39698 records a Unknown severity vulnerability in io_uring/futex: ensure io_futex_wait() cleans up properly on failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <d9f93172820a53ab42c4b0e5e65291f4f9d00ad2 || >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <d34c04152df517c59979b4bf2a47f491e06d3256 || >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <508c1314b342b78591f51c4b5dadee31a88335df | d9f93172820a53ab42c4b0e5e65291f4f9d00ad2, d34c04152df517c59979b4bf2a47f491e06d3256, 508c1314b342b78591f51c4b5dadee31a88335df |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on failure The io_futex_data is allocated upfront and assigned to the io_kiocb async_data field, but the request isn't marked with REQ_F_ASYNC_DATA at that point. Those two should always go together, as the flag tells io_uring whether the field is valid or not. Additionally, on failure cleanup, the futex handler frees the data but does not clear ->async_data. Clear the data and the flag in the error path as well. Thanks to Trend Micro Zero Day Initiative and particularly ReDress for reporting this.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39698 records a Unknown severity vulnerability in io_uring/futex: ensure io_futex_wait() cleans up properly on failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <d9f93172820a53ab42c4b0e5e65291f4f9d00ad2 || >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <d34c04152df517c59979b4bf2a47f491e06d3256 || >=194bb58c6090e39bd7d9b9c888a079213628e1f6 <508c1314b342b78591f51c4b5dadee31a88335df | d9f93172820a53ab42c4b0e5e65291f4f9d00ad2, d34c04152df517c59979b4bf2a47f491e06d3256, 508c1314b342b78591f51c4b5dadee31a88335df |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on failure The io_futex_data is allocated upfront and assigned to the io_kiocb async_data field, but the request isn't marked with REQ_F_ASYNC_DATA at that point. Those two should always go together, as the flag tells io_uring whether the field is valid or not. Additionally, on failure cleanup, the futex handler frees the data but does not clear ->async_data. Clear the data and the flag in the error path as well. Thanks to Trend Micro Zero Day Initiative and particularly ReDress for reporting this.
Quoted source text, attributed separately from HOL analysis.