https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:33:08 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23357 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: mcp251x: fix deadlock in error path of mcp251x_open</p> <p>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.</p> <p>This issue is similar to the one fixed in commit 7dd9c26bd6cf (&#34;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&#34;) but for the error path.</p> <p>To solve this issue move the call to free_irq() after the lock is released. Setting `priv-&gt;force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>can: mcp251x: fix deadlock in error path of mcp251x_open</p> <p>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.</p> <p>This issue is similar to the one fixed in commit 7dd9c26bd6cf (&#34;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&#34;) but for the error path.</p> <p>To solve this issue move the call to free_irq() after the lock is released. Setting `priv-&gt;force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.</p> https://vulnerability.circl.lu/vuln/cve-2026-23357