CVE-2024-56584
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-770 · Allocation without limits
- Record status
- Modified
Affected
- Linux Kernel < 6.1.120
- Linux Kernel < 6.6.66
- Linux Kernel < 6.12.5
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-56584.md and follow it. Check whether this project is affected by CVE-2024-56584. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e
- https://git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4
- https://git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0
- https://git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d
References
- https://git.kernel.org/stable/c/3a84fa784710990964c1e35df743851ab2863898
- https://git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e
- https://git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4
- https://git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0
- https://git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d
- https://git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html