CVE-2026-23357

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.

CVSS 3.1

5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

0.1% chance of exploitation in the next 30 days; higher than 1% of CVEs (scores of 2026-10-25)

CWE

CWE-667

Published

2026-03-25

Modified

2026-10-15

Record from

the NVD, synced 2026-10-19

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/256f0cff6e946c570392bda1d01a65e789a7afd0
• https://git.kernel.org/stable/c/38063cc435b69d56e76f947c10d336fcb2953508
• https://git.kernel.org/stable/c/416c18ecddafab0ed09be1e7b9d2f448f3d4db16
• https://git.kernel.org/stable/c/739454057572cb0948658d1142f3fa2c6966465c
• https://git.kernel.org/stable/c/ab3f894de216f4a62adc3b57e9191888cbf26885

Check your stackJSON