- Vulnerability/
- CVE-2024-56584
CVE-2024-56584: io_uring/tctx: work around xa_store() allocation error issue
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 | ||
| debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56584
- https://nvd.nist.gov/vuln/detail/CVE-2024-56584
- https://launchpad.net/bugs/cve/CVE-2024-56584
- https://security-tracker.debian.org/tracker/CVE-2024-56584
- https://ubuntu.com/security/CVE-2024-56584
- https://git.kernel.org/linus/7eb75ce7527129d7f1fee6951566af409a37a1c4
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.
- agent/title
- agent/severity
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/author
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux foundation
- canonical/linux kernel
- package-manager/debian