CVE-2025-39698
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rhel | 9 | fixed | |
| sles | affected | | |
| rocky | 9 | fixed | |
| debian | bookworm | fixed | 0 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.16.5-1 |
| debian | sid | fixed | 6.16.5-1 |
| debian | trixie | fixed | 6.12.48-1 |
| almalinux | 9 | fixed | kernel-devel-5.14.0-570.49.1.el9_6.aarch64.rpm |
References
- https://access.redhat.com/errata/RHSA-2025:16880
- https://www.suse.com/security/cve/CVE-2025-39698.html
- https://errata.rockylinux.org/RLSA-2025:16880
- https://security-tracker.debian.org/tracker/CVE-2025-39698
- https://bugzilla.redhat.com/2383916
- https://bugzilla.redhat.com/2388928
- https://bugzilla.redhat.com/2393166
- https://bugzilla.redhat.com/2393511
- https://bugzilla.redhat.com/2393519
- https://errata.almalinux.org/9/ALSA-2025-16880.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.