Bug 2393519 (CVE-2025-39698) - CVE-2025-39698 kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure
Summary: CVE-2025-39698 kernel: io_uring/futex: ensure io_futex_wait() cleans up prope...
Keywords:
Status: NEW
Alias: CVE-2025-39698
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-05 18:03 UTC by OSIDB Bzimport
Modified: 2025-10-16 08:15 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:16880 0 None None None 2025-09-29 05:05:45 UTC
Red Hat Product Errata RHSA-2025:16904 0 None None None 2025-09-29 07:48:02 UTC

Description OSIDB Bzimport 2025-09-05 18:03:55 UTC
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.

Comment 5 errata-xmlrpc 2025-09-29 05:05:44 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:16880 https://access.redhat.com/errata/RHSA-2025:16880

Comment 6 errata-xmlrpc 2025-09-29 07:48:01 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:16904 https://access.redhat.com/errata/RHSA-2025:16904


Note You need to log in before you can comment on or make changes to this bug.