{"api_version":"1","generated_at":"2026-07-23T10:35:50+00:00","cve":"CVE-2024-56584","urls":{"html":"https://cve.report/CVE-2024-56584","api":"https://cve.report/api/cve/CVE-2024-56584.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2024-56584","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2024-56584"},"summary":{"title":"io_uring/tctx: work around xa_store() allocation error issue","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/tctx: work around xa_store() allocation error issue\n\nsyzbot triggered the following WARN_ON:\n\nWARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51\n\nwhich is the\n\nWARN_ON_ONCE(!xa_empty(&tctx->xa));\n\nsanity check in __io_uring_free() when a io_uring_task is going through\nits final put. The syzbot test case includes injecting memory allocation\nfailures, and it very much looks like xa_store() can fail one of its\nmemory allocations and end up with ->head being non-NULL even though no\nentries exist in the xarray.\n\nUntil this issue gets sorted out, work around it by attempting to\niterate entries in our xarray, and WARN_ON_ONCE() if one is found.","state":"PUBLISHED","assigner":"Linux","published_at":"2024-12-27 15:15:17","updated_at":"2026-04-18 09:16:09"},"problem_types":["CWE-770"],"metrics":[{"version":"3.1","source":"nvd@nist.gov","type":"Primary","score":"5.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}}],"references":[{"url":"https://git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0","name":"https://git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d","name":"https://git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e","name":"https://git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3a84fa784710990964c1e35df743851ab2863898","name":"https://git.kernel.org/stable/c/3a84fa784710990964c1e35df743851ab2863898","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9","name":"https://git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4","name":"https://git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html","name":"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56584","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56584","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e e05c070b401f6365c503e2b59f091331965c4fb9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e 3a84fa784710990964c1e35df743851ab2863898 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e 94ad56f61b873ffeebcc620d451eacfbdf9d40f0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e 42882b583095dcf747da6e3af1daeff40e27033e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e d5b2ddf1f90c7248eff9630b95895c8950f2f36d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e 7eb75ce7527129d7f1fee6951566af409a37a1c4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.10.253 5.10.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15.203 5.15.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.120 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.66 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.5 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.13 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2024","cve_id":"56584","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"linux","cpe5":"linux_kernel","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2025-11-03T20:50:01.079Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html"}],"title":"CVE Program Container"}],"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["io_uring/tctx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"e05c070b401f6365c503e2b59f091331965c4fb9","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"},{"lessThan":"3a84fa784710990964c1e35df743851ab2863898","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"},{"lessThan":"94ad56f61b873ffeebcc620d451eacfbdf9d40f0","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"},{"lessThan":"42882b583095dcf747da6e3af1daeff40e27033e","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"},{"lessThan":"d5b2ddf1f90c7248eff9630b95895c8950f2f36d","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"},{"lessThan":"7eb75ce7527129d7f1fee6951566af409a37a1c4","status":"affected","version":"2b188cc1bb857a9d4701ae59aa7768b5124e262e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["io_uring/tctx.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.1"},{"lessThan":"5.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"5.10.*","status":"unaffected","version":"5.10.253","versionType":"semver"},{"lessThanOrEqual":"5.15.*","status":"unaffected","version":"5.15.203","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.120","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.66","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"6.13","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.10.253","versionStartIncluding":"5.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"5.15.203","versionStartIncluding":"5.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.120","versionStartIncluding":"5.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.66","versionStartIncluding":"5.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.5","versionStartIncluding":"5.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.13","versionStartIncluding":"5.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/tctx: work around xa_store() allocation error issue\n\nsyzbot triggered the following WARN_ON:\n\nWARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51\n\nwhich is the\n\nWARN_ON_ONCE(!xa_empty(&tctx->xa));\n\nsanity check in __io_uring_free() when a io_uring_task is going through\nits final put. The syzbot test case includes injecting memory allocation\nfailures, and it very much looks like xa_store() can fail one of its\nmemory allocations and end up with ->head being non-NULL even though no\nentries exist in the xarray.\n\nUntil this issue gets sorted out, work around it by attempting to\niterate entries in our xarray, and WARN_ON_ONCE() if one is found."}],"providerMetadata":{"dateUpdated":"2026-04-18T08:56:45.522Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9"},{"url":"https://git.kernel.org/stable/c/3a84fa784710990964c1e35df743851ab2863898"},{"url":"https://git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0"},{"url":"https://git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e"},{"url":"https://git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d"},{"url":"https://git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4"}],"title":"io_uring/tctx: work around xa_store() allocation error issue","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2024-56584","datePublished":"2024-12-27T14:50:52.735Z","dateReserved":"2024-12-27T14:03:06.001Z","dateUpdated":"2026-04-18T08:56:45.522Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2024-12-27 15:15:17","lastModifiedDate":"2026-04-18 09:16:09","problem_types":["CWE-770"],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":3.6}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.1","versionEndExcluding":"6.1.120","matchCriteriaId":"2B2F277A-44C4-438C-9ECE-25B9E59E970E"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.2","versionEndExcluding":"6.6.66","matchCriteriaId":"29A976AD-B9AB-4A95-9F08-7669F8847EB9"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.7","versionEndExcluding":"6.12.5","matchCriteriaId":"9501D045-7A94-42CA-8B03-821BE94A65B7"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2024","CveId":"56584","Ordinal":"1","Title":"io_uring/tctx: work around xa_store() allocation error issue","CVE":"CVE-2024-56584","Year":"2024"},"notes":[{"CveYear":"2024","CveId":"56584","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/tctx: work around xa_store() allocation error issue\n\nsyzbot triggered the following WARN_ON:\n\nWARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51\n\nwhich is the\n\nWARN_ON_ONCE(!xa_empty(&tctx->xa));\n\nsanity check in __io_uring_free() when a io_uring_task is going through\nits final put. The syzbot test case includes injecting memory allocation\nfailures, and it very much looks like xa_store() can fail one of its\nmemory allocations and end up with ->head being non-NULL even though no\nentries exist in the xarray.\n\nUntil this issue gets sorted out, work around it by attempting to\niterate entries in our xarray, and WARN_ON_ONCE() if one is found.","Type":"Description","Title":"io_uring/tctx: work around xa_store() allocation error issue"}]}}}