CVE-2024-46791: can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3a49b6b1caf5cefc05264d29079d52c99cb188e0, 513c8fc189b52f7922e36bdca58997482b198f0e, 7dd9c26bd6cf679bcfdef01a8659791aa6487a29.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3a49b6b1caf5cefc05264d29079d52c99cb188e0, 513c8fc189b52f7922e36bdca58997482b198f0e, 7dd9c26bd6cf679bcfdef01a8659791aa6487a29 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.5 and later · before 5.10.226
- linux linux kernel5.11 and later · before 5.15.167
- linux linux kernel5.16 and later · before 6.1.110
- linux linux kernel6.2 and later · before 6.6.51
- linux linux kernel6.7 and later · before 6.10.10
- linux linux kernel6.11
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before 3a49b6b1caf5cefc05264d29079d52c99cb188e0affected · git
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before 513c8fc189b52f7922e36bdca58997482b198f0eaffected · git
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before f7ab9e14b23a3eac6714bdc4dba244d8aa1ef646affected · git
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before 8fecde9c3f9a4b97b68bb97c9f47e5b662586ba7affected · git
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before e554113a1cd2a9cfc6c7af7bdea2141c5757e188affected · git
- 8ce8c0abcba314e1fe954a1840f6568bf5aef2ef and later · before 7dd9c26bd6cf679bcfdef01a8659791aa6487a29affected · git
- before 5.5not affected · semver
- 5.10.226 and later · up to and including 5.10.*not affected · semver
- 5.15.167 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.112-1 | 6.1.112-1 |
| Debian:13 | linux | before 6.10.11-1 | 6.10.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-46789Sep 18, 2024 · mm/slub: add check for s->flags in the alloc_tagging_slab_free_hook22Monitor
- ← EarlierCVE-2024-46790Sep 18, 2024 · codetag: debug: mark codetags for poisoned page as empty22Monitor
- Later →CVE-2024-46792Sep 18, 2024 · riscv: misaligned: Restrict user access to kernel memory13Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a49b6b1caf5cefc05264d29079d52c99cb188e0 | Vendor (CNA) |
| Linux Linux | 513c8fc189b52f7922e36bdca58997482b198f0e | Vendor (CNA) |
| Linux Linux | 7dd9c26bd6cf679bcfdef01a8659791aa6487a29 | Vendor (CNA) |
| Linux Linux | 8fecde9c3f9a4b97b68bb97c9f47e5b662586ba7 | Vendor (CNA) |
| Linux Linux | e554113a1cd2a9cfc6c7af7bdea2141c5757e188 | Vendor (CNA) |
| Linux Linux | f7ab9e14b23a3eac6714bdc4dba244d8aa1ef646 | Vendor (CNA) |
| debian:linux | 6.1.112-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1498 · Sep 19, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/513c8fc189b52f7922e36bdca58997482b198f0e
- git.kernel.org/stable/c/7dd9c26bd6cf679bcfdef01a8659791aa6487a29
- git.kernel.org/stable/c/8fecde9c3f9a4b97b68bb97c9f47e5b662586ba7
- git.kernel.org/stable/c/e554113a1cd2a9cfc6c7af7bdea2141c5757e188
- git.kernel.org/stable/c/f7ab9e14b23a3eac6714bdc4dba244d8aa1ef646
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.