First published: Fri Dec 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: io_uring/tctx: work around xa_store() allocation error issue syzbot triggered the following WARN_ON: WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51 which is the WARN_ON_ONCE(!xa_empty(&tctx->xa)); sanity check in __io_uring_free() when a io_uring_task is going through its final put. The syzbot test case includes injecting memory allocation failures, and it very much looks like xa_store() can fail one of its memory allocations and end up with ->head being non-NULL even though no entries exist in the xarray. Until this issue gets sorted out, work around it by attempting to iterate entries in our xarray, and WARN_ON_ONCE() if one is found.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-56584 has been classified with a severity level that may impact system stability due to allocation errors in the io_uring subsystem.
To fix CVE-2024-56584, update your Linux kernel to the latest stable version where this vulnerability has been addressed.
CVE-2024-56584 affects the Linux kernel, specifically the versions utilizing the io_uring subsystem.
Exploitation of CVE-2024-56584 may lead to warnings in the system logs related to io_uring operations and potential instability.
As of now, there is no evidence to suggest that CVE-2024-56584 is being actively exploited in the wild.