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-41080io_uring: fix possible deadlock in io_register_iowq_max_workers()

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring: fix possible deadlock in io_register_iowq_max_workers() The io_register_iowq_max_workers() function calls io_put_sq_data(), which acquires the sqd->lock without releasing the uring_lock. Similar to the commit 009ad9f0c6ee ("io_uring: drop ctx->uring_lock before acquiring sqd->lock"), this can lead to a potential deadlock situation. To resolve this issue, the uring_lock is released before calling io_put_sq_data(), and then it is re-acquired after the function call. This change ensures that the locks are acquired in the correct order, preventing the possibility of a deadlock.

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 22 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-41080, 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.20% · top 89% of all CVEs (19 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 – < b17397a0a5c56e111f61cb5b77d162664dc00de9
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 97ed7ff58de66c544692b3c2b988f3f594348de0
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < fdacd09f2ddf7a00787291f08ee48c0421e5b709
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 950ac86cff338ab56e2eaf611f4936ee34893b63
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < b571a367502c7ef94c688ef9c7f7d69a2ce3bcca
    • affected 2b188cc1bb857a9d4701ae59aa7768b5124e262e – < 73254a297c2dd094abec7c9efee32455ae875bdf
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.10.230 – ≤ 5.10.*
    • unaffected 5.15.173 – ≤ 5.15.*
    • unaffected 6.1.118 – ≤ 6.1.*
    • unaffected 6.6.62 – ≤ 6.6.*
    • unaffected 6.9.11 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .