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

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-03-25 · updated 2026-10-15
Weakness: CWE-667

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.

Affected products

Linux kernel: from 2.6.34.1 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.77; from 6.13 before 6.18.17 — fixed in 5.10.253, 5.15.203, 6.1.167, 6.12.77, 6.18.17, 6.19.7

How to fix

Upgrade to a fixed version: Linux kernel 5.10.253, 5.15.203, 6.1.167, 6.12.77. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-23357 or the next vulnerability affects your stack