io_uring/tctx: work around xa_store() allocation error issue
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.253, 5.15.203, 6.1.120, 6.12.5, 6.6.66
- CVEs
- CVE-2024-56584
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 07:39 UTC · Revision 1
Source evidence
io_uring/tctx: work around xa_store() allocation error issue
core-osv · Original sourcePublished 27 Dec 2024, 14:50 UTC
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.
osv:CVE-2024-56584
Kernel
Fixed versions: 5.10.253, 5.15.203, 6.1.120, 6.6.66, 6.12.5
Complete source record
{
"id": "07a46f524b56518576d7899d377c63e006d26c41d1af3151168c748e3a8c3da4",
"url": "https://osv.dev/vulnerability/CVE-2024-56584",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "io_uring/tctx: work around xa_store() allocation error issue",
"summary": "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.",
"evidence": "osv:CVE-2024-56584",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.253",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.203",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.120",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.66",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-56584",
"aliases": [
"CVE-2024-56584"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2b188cc1bb857a9d4701ae59aa7768b5124e262e"
},
{
"fixed": "e05c070b401f6365c503e2b59f091331965c4fb9"
},
{
"fixed": "3a84fa784710990964c1e35df743851ab2863898"
},
{
"fixed": "94ad56f61b873ffeebcc620d451eacfbdf9d40f0"
},
{
"fixed": "42882b583095dcf747da6e3af1daeff40e27033e"
},
{
"fixed": "d5b2ddf1f90c7248eff9630b95895c8950f2f36d"
},
{
"fixed": "7eb75ce7527129d7f1fee6951566af409a37a1c4"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56584.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.1.0"
},
{
"fixed": "5.10.253"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.203"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.120"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.66"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56584.json"
}
}
],
"modified": "2026-10-28T02:30:50.364027271Z",
"provider": "osv",
"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",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56584.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-56584",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56584.json"
}
},
"related_cves": [
{
"value": "CVE-2024-56584",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518661,
"published_at": "2024-12-27T14:50:52.735+00:00"
}