CVE-2024-56584: io_uring/tctx: work around xa_store() allocation error issue
In the Linux kernel, the following vulnerability has been resolved:
iouring/tctx: work around xastore() allocation error issue
syzbot triggered the following WARNON:
WARNING: CPU: 0 PID: 16 at iouring/tctx.c:51 iouringfree+0xfa/0x140 iouring/tctx.c:51
which is the
WARNONONCE(!xaempty(&tctx->xa));
sanity check in iouringfree() when a iouringtask is going through its final put. The syzbot test case includes injecting memory allocation failures, and it very much looks like xastore() 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 WARNONONCE() if one is found.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56584?
CVE-2024-56584 has been classified with a severity level that may impact system stability due to allocation errors in the io_uring subsystem.
How do I fix CVE-2024-56584?
To fix CVE-2024-56584, update your Linux kernel to the latest stable version where this vulnerability has been addressed.
What systems are affected by CVE-2024-56584?
CVE-2024-56584 affects the Linux kernel, specifically the versions utilizing the io_uring subsystem.
What are the symptoms of CVE-2024-56584 exploitation?
Exploitation of CVE-2024-56584 may lead to warnings in the system logs related to io_uring operations and potential instability.
Is CVE-2024-56584 actively being exploited in the wild?
As of now, there is no evidence to suggest that CVE-2024-56584 is being actively exploited in the wild.