Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-56584

io_uring/tctx: work around xa_store() allocation error issue

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-56584, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < e05c070b401f6365c503e2b59f091331965c4fb9
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 3a84fa784710990964c1e35df743851ab2863898
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 94ad56f61b873ffeebcc620d451eacfbdf9d40f0
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 42882b583095dcf747da6e3af1daeff40e27033e
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < d5b2ddf1f90c7248eff9630b95895c8950f2f36d
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 7eb75ce7527129d7f1fee6951566af409a37a1c4
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.66 – ≤ 6.6.*
    • unaffected 6.12.5 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-56584 badge
[![CVE-2024-56584](https://cveledger.app/badge/CVE-2024-56584.svg)](https://cveledger.app/cve/CVE-2024-56584)

Record last updated .