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-46791can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open

Description

In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open The mcp251x_hw_wake() function is called with the mpc_lock mutex held and disables the interrupt handler so that no interrupts can be processed while waking the device. If an interrupt has already occurred then waiting for the interrupt handler to complete will deadlock because it will be trying to acquire the same mutex. CPU0 CPU1 ---- ---- mcp251x_open() mutex_lock(&priv->mcp_lock) request_threaded_irq() <interrupt> mcp251x_can_ist() mutex_lock(&priv->mcp_lock) mcp251x_hw_wake() disable_irq() <-- deadlock Use disable_irq_nosync() instead because the interrupt handler does everything while holding the mutex so it doesn't matter if it's still running.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 20 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-46791, 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.16% · top 94% of all CVEs (14 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 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < 3a49b6b1caf5cefc05264d29079d52c99cb188e0
    • affected 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < 513c8fc189b52f7922e36bdca58997482b198f0e
    • affected 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < f7ab9e14b23a3eac6714bdc4dba244d8aa1ef646
    • affected 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < 8fecde9c3f9a4b97b68bb97c9f47e5b662586ba7
    • affected 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < e554113a1cd2a9cfc6c7af7bdea2141c5757e188
    • affected 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef – < 7dd9c26bd6cf679bcfdef01a8659791aa6487a29
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.110 – ≤ 6.1.*
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .