CVE-2025-39698: io_uring/futex: ensure io_futex_wait() cleans up properly on failure
Vulnerability summary
CVE-2025-39698 is a high (CVSS 7.8) Use After Free vulnerability in linux. EPSS estimates a 0.19% chance of exploitation in the next 30 days, higher than 9.1% of scored vulnerabilities.
Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 20 · Related 17Timeline
- 05-09-2025PublishedVulnerability first disclosed.
- 05-08-2026Last modifiedVulnerability information updated.
Description
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.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated7.8HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HDiffers
- NVDNIST5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HDiffers
EPSS trend
Probability
0.19%
Chance of exploitation in the next 30 days
Percentile
9%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.19% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
- CWE-672Operation on a Resource after Expiration or ReleaseThe product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
Affected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu122 products
- linux< 6.8.0-94.96
- linux-allwinner-5.19All versions (No fix recorded)
- linux-aws< 6.8.0-1045.47
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 194bb58c6090e39bd7d9b9c888a079213628e1f6, < d9f93172820a53ab42c4b0e5e65291f4f9d00ad2 | ≥ 194bb58c6090e39bd7d9b9c888a079213628e1f6, < d34c04152df517c59979b4bf2a47f491e06d3256 | ≥ 194bb58c6090e39bd7d9b9c888a079213628e1f6, < 508c1314b342b78591f51c4b5dadee31a88335df | 6.7
- linux_kernel≥ 6.7, < 6.12.44 | ≥ 6.13, < 6.16.4 | 6.17:rc1 | 6.17:rc2
Debian1 product
- linux< 6.12.48-1 | < 6.16.5-1
3 vendors · 125 products
References
17 links- www.zerodayinitiative.com/advisories/ZDI-25-915/Third Party Advisory