<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 19:37:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46791 — can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46791</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_hw_wake() function is called with the mpc_lock mutex held and
disables the interrupt handler so that no interrupts can be processed while
waking the device. If an interrupt has already occurred then waiting for
the interrupt handler to complete will deadlock because it will be trying
to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;CPU0                           CPU1
----                           ----
mcp251x_open()
 mutex_lock(&amp;amp;priv-&amp;gt;mcp_lock)
  request_threaded_irq()
                               &amp;lt;interrupt&amp;gt;
                               mcp251x_can_ist()
                                mutex_lock(&amp;amp;priv-&amp;gt;mcp_lock)
  mcp251x_hw_wake()
   disable_irq() &amp;lt;-- deadlock&lt;/p&gt;
&lt;p&gt;Use disable_irq_nosync() instead because the interrupt handler does
everything while holding the mutex so it doesn&amp;#39;t matter if it&amp;#39;s still
running.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_hw_wake() function is called with the mpc_lock mutex held and
disables the interrupt handler so that no interrupts can be processed while
waking the device. If an interrupt has already occurred then waiting for
the interrupt handler to complete will deadlock because it will be trying
to acquire the same mutex.&lt;/p&gt;
&lt;p&gt;CPU0                           CPU1
----                           ----
mcp251x_open()
 mutex_lock(&amp;amp;priv-&amp;gt;mcp_lock)
  request_threaded_irq()
                               &amp;lt;interrupt&amp;gt;
                               mcp251x_can_ist()
                                mutex_lock(&amp;amp;priv-&amp;gt;mcp_lock)
  mcp251x_hw_wake()
   disable_irq() &amp;lt;-- deadlock&lt;/p&gt;
&lt;p&gt;Use disable_irq_nosync() instead because the interrupt handler does
everything while holding the mutex so it doesn&amp;#39;t matter if it&amp;#39;s still
running.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46791</guid>
    </item>
  </channel>
</rss>
