<?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>Tue, 29 Sep 2026 13:40:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54152 — can: j1939: prevent deadlock by moving j1939_sk_errqueue()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54152</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: j1939: prevent deadlock by moving j1939_sk_errqueue()&lt;/p&gt;
&lt;p&gt;This commit addresses a deadlock situation that can occur in certain
scenarios, such as when running data TP/ETP transfer and subscribing to
the error queue while receiving a net down event. The deadlock involves
locks in the following order:&lt;/p&gt;
&lt;p&gt;3
  j1939_session_list_lock -&amp;gt;  active_session_list_lock
  j1939_session_activate
  ...
  j1939_sk_queue_activate_next -&amp;gt; sk_session_queue_lock
  ...
  j1939_xtp_rx_eoma_one&lt;/p&gt;
&lt;p&gt;2
  j1939_sk_queue_drop_all  -&amp;gt;  sk_session_queue_lock
  ...
  j1939_sk_netdev_event_netdown -&amp;gt; j1939_socks_lock
  j1939_netdev_notify&lt;/p&gt;
&lt;p&gt;1
  j1939_sk_errqueue -&amp;gt; j1939_socks_lock
  __j1939_session_cancel -&amp;gt; active_session_list_lock
  j1939_tp_rxtimer&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;priv-&amp;gt;active_session_list_lock);
                               lock(&amp;amp;jsk-&amp;gt;sk_session_queue_lock);
                               lock(&amp;amp;priv-&amp;gt;active_session_list_lock);
  lock(&amp;amp;priv-&amp;gt;j1939_socks_lock);&lt;/p&gt;
&lt;p&gt;The solution implemented in this commit is to move the
j1939_sk_errqueue() call out of the active_session_list_lock context,
thus preventing the deadlock situation.&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: j1939: prevent deadlock by moving j1939_sk_errqueue()&lt;/p&gt;
&lt;p&gt;This commit addresses a deadlock situation that can occur in certain
scenarios, such as when running data TP/ETP transfer and subscribing to
the error queue while receiving a net down event. The deadlock involves
locks in the following order:&lt;/p&gt;
&lt;p&gt;3
  j1939_session_list_lock -&amp;gt;  active_session_list_lock
  j1939_session_activate
  ...
  j1939_sk_queue_activate_next -&amp;gt; sk_session_queue_lock
  ...
  j1939_xtp_rx_eoma_one&lt;/p&gt;
&lt;p&gt;2
  j1939_sk_queue_drop_all  -&amp;gt;  sk_session_queue_lock
  ...
  j1939_sk_netdev_event_netdown -&amp;gt; j1939_socks_lock
  j1939_netdev_notify&lt;/p&gt;
&lt;p&gt;1
  j1939_sk_errqueue -&amp;gt; j1939_socks_lock
  __j1939_session_cancel -&amp;gt; active_session_list_lock
  j1939_tp_rxtimer&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;priv-&amp;gt;active_session_list_lock);
                               lock(&amp;amp;jsk-&amp;gt;sk_session_queue_lock);
                               lock(&amp;amp;priv-&amp;gt;active_session_list_lock);
  lock(&amp;amp;priv-&amp;gt;j1939_socks_lock);&lt;/p&gt;
&lt;p&gt;The solution implemented in this commit is to move the
j1939_sk_errqueue() call out of the active_session_list_lock context,
thus preventing the deadlock situation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54152</guid>
    </item>
  </channel>
</rss>
