{"schema_version":"1.7.5","id":"CVE-2026-23357","published":"2026-03-25T10:27:41.299Z","modified":"2026-07-15T01:49:06.305387433Z","related":["SUSE-SU-2026:21834-1","SUSE-SU-2026:21841-1","SUSE-SU-2026:21845-1","SUSE-SU-2026:21860-1","SUSE-SU-2026:21876-1","SUSE-SU-2026:21877-1","SUSE-SU-2026:21916-1","SUSE-SU-2026:21919-1","SUSE-SU-2026:2217-1","SUSE-SU-2026:2238-1","openSUSE-SU-2026:20826-1"],"summary":"can: mcp251x: fix deadlock in error path of mcp251x_open","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: mcp251x: fix deadlock in error path of mcp251x_open\n\nThe mcp251x_open() function call free_irq() in its error path with the\nmpc_lock mutex held. But if an interrupt already occurred the\ninterrupt handler will be waiting for the mpc_lock and free_irq() will\ndeadlock waiting for the handler to finish.\n\nThis issue is similar to the one fixed in commit 7dd9c26bd6cf (\"can:\nmcp251x: fix deadlock if an interrupt occurs during mcp251x_open\") but\nfor the error path.\n\nTo solve this issue move the call to free_irq() after the lock is\nreleased. Setting `priv->force_quit = 1` beforehand ensure that the IRQ\nhandler will exit right away once it acquired the lock.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"bf66f3736a945dd4e92d86427276c6eeab0a6c1d"},{"fixed":"739454057572cb0948658d1142f3fa2c6966465c"},{"fixed":"416c18ecddafab0ed09be1e7b9d2f448f3d4db16"},{"fixed":"256f0cff6e946c570392bda1d01a65e789a7afd0"},{"fixed":"b73832292cd914e87a55e863ba4413a907e7db6b"},{"fixed":"38063cc435b69d56e76f947c10d336fcb2953508"},{"fixed":"d27f12c3f5e85efc479896af4a69eccb37f75e8e"},{"fixed":"e728f444c913a91d290d1824b4770780bbd6378e"},{"fixed":"ab3f894de216f4a62adc3b57e9191888cbf26885"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23357.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.34"},{"fixed":"5.10.253"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.203"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.7"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23357.json"}}],"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/256f0cff6e946c570392bda1d01a65e789a7afd0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/38063cc435b69d56e76f947c10d336fcb2953508"},{"type":"WEB","url":"https://git.kernel.org/stable/c/416c18ecddafab0ed09be1e7b9d2f448f3d4db16"},{"type":"WEB","url":"https://git.kernel.org/stable/c/739454057572cb0948658d1142f3fa2c6966465c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ab3f894de216f4a62adc3b57e9191888cbf26885"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b73832292cd914e87a55e863ba4413a907e7db6b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d27f12c3f5e85efc479896af4a69eccb37f75e8e"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e728f444c913a91d290d1824b4770780bbd6378e"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23357.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23357"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23357.json"}}