can: mcp251x: fix deadlock in error path of mcp251x_open
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
2.6.34
- KernelLinux
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
References 8
git.kernel.org
- stable/c/739454057572cb0948658d1142f3fa2c6966465c
- stable/c/416c18ecddafab0ed09be1e7b9d2f448f3d4db16
- stable/c/256f0cff6e946c570392bda1d01a65e789a7afd0
- stable/c/b73832292cd914e87a55e863ba4413a907e7db6b
- stable/c/38063cc435b69d56e76f947c10d336fcb2953508
- stable/c/d27f12c3f5e85efc479896af4a69eccb37f75e8e
- stable/c/e728f444c913a91d290d1824b4770780bbd6378e
- stable/c/ab3f894de216f4a62adc3b57e9191888cbf26885