Device initialization hang via interrupt-handler deadlock
Published Sep 18, 2024 · Updated May 11, 2026
Improper locking in the Linux mcp251x CAN driver allows attackers to hang device initialization when an interrupt races with opening. mcp251x_open holds mcp_lock while mcp251x_hw_wake calls disable_irq, which waits for mcp251x_can_ist even when that handler is blocked on the same mutex. Reachability requires an MCP251x CAN controller and the narrow timing window in which its interrupt handler begins while the interface is opening; the resulting deadlock prevents the open operation from completing.
Summary
What happened
Improper locking in the Linux mcp251x CAN driver allows attackers to hang device initialization when an interrupt races with opening. mcp251x_open holds mcp_lock while mcp251x_hw_wake calls disable_irq, which waits for mcp251x_can_ist even when that handler is blocked on the same mutex. Reachability requires an MCP251x CAN controller and the narrow timing window in which its interrupt handler begins while the interface is opening; the resulting deadlock prevents the open operation from completing.
The record
- CVE
- CVE-2024-46791
- Published
- Sep 18, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <3a49b6b1caf5cefc05264d29079d52c99cb188e0
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <513c8fc189b52f7922e36bdca58997482b198f0e
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <7dd9c26bd6cf679bcfdef01a8659791aa6487a29
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <8fecde9c3f9a4b97b68bb97c9f47e5b662586ba7
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <e554113a1cd2a9cfc6c7af7bdea2141c5757e188
- Affected versionversion=8ce8c0abcba314e1fe954a1840f6568bf5aef2ef <f7ab9e14b23a3eac6714bdc4dba244d8aa1ef646
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo