CVE-2024-56584

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2024-56584
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-56584.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-56584
Downstream
Related
Published
2024-12-27T14:50:52.735Z
Modified
2026-03-20T12:39:52.926407Z
Summary
io_uring/tctx: work around xa_store() allocation error issue
Details

In the Linux kernel, the following vulnerability has been resolved:

iouring/tctx: work around xastore() allocation error issue

syzbot triggered the following WARN_ON:

WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 _iouringfree+0xfa/0x140 iouring/tctx.c:51

which is the

WARNONONCE(!xa_empty(&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.

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56584.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
2b188cc1bb857a9d4701ae59aa7768b5124e262e
Fixed
94ad56f61b873ffeebcc620d451eacfbdf9d40f0
Fixed
42882b583095dcf747da6e3af1daeff40e27033e
Fixed
d5b2ddf1f90c7248eff9630b95895c8950f2f36d
Fixed
7eb75ce7527129d7f1fee6951566af409a37a1c4

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-56584.json"