VulnerabilityPublished 25 Mar 2026Updated 5 Nov 2026

CVE-2026-23357: Linux kernel · can: mcp251x: fix deadlock in error path of mcp251x_open

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e728f444c913a91d290d1824b4770780bbd6378e : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in e728f444c913a91d290d1824b4770780bbd6378e, d27f12c3f5e85efc479896af4a69eccb37f75e8e, b73832292cd914e87a55e863ba4413a907e7db6b +5

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < e728f444c913a91d290d1824b4770780bbd6378e	Fixed in e728f444c913a91d290d1824b4770780bbd6378e
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < d27f12c3f5e85efc479896af4a69eccb37f75e8e	Fixed in d27f12c3f5e85efc479896af4a69eccb37f75e8e
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < b73832292cd914e87a55e863ba4413a907e7db6b	Fixed in b73832292cd914e87a55e863ba4413a907e7db6b
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < ab3f894de216f4a62adc3b57e9191888cbf26885	Fixed in ab3f894de216f4a62adc3b57e9191888cbf26885
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < 739454057572cb0948658d1142f3fa2c6966465c	Fixed in 739454057572cb0948658d1142f3fa2c6966465c
LinuxLinux	Affected ≥ bf66f3736a945dd4e92d86427276c6eeab0a6c1d, < 38063cc435b69d56e76f947c10d336fcb2953508	Fixed in 38063cc435b69d56e76f947c10d336fcb2953508

Description

In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish. This issue is similar to the one fixed in commit 7dd9c26bd6cf ("can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open") but for the error path. To solve this issue move the call to free_irq() after the lock is released. Setting `priv->force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.

References

Community reviews

Loading reviews…