CVE-2024-56584: Linux kernel · io_uring/tctx: work around xa_store() allocation error issue
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 5 Nov 2026, 23:23 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
Description
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.
References
- git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9 (opens in a new tab)
- git.kernel.org/stable/c/3a84fa784710990964c1e35df743851ab2863898 (opens in a new tab)
- git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0 (opens in a new tab)
- git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e (opens in a new tab)
- git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d (opens in a new tab)
- git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)