CVE-2025-39698
05.09.2025, 18:15
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.Enginsight
| Vendor | Product | Version |
|---|---|---|
| linux | linux_kernel | 6.7 ≤ 𝑥 < 6.12.44 |
| linux | linux_kernel | 6.13 ≤ 𝑥 < 6.16.4 |
| linux | linux_kernel | 6.17:rc1 |
| linux | linux_kernel | 6.17:rc2 |
𝑥
= Vulnerable software versions
Debian Releases
Common Weakness Enumeration
- CWE-416 - Use After FreeReferencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
- CWE-672 - Operation on a Resource after Expiration or ReleaseThe software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
Vulnerability Media Exposure