<?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 10:44:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49195 — net: dsa: fix panic on shutdown if multi-chip tree failed to probe</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49195</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;net: dsa: fix panic on shutdown if multi-chip tree failed to probe&lt;/p&gt;
&lt;p&gt;DSA probing is atypical because a tree of devices must probe all at
once, so out of N switches which call dsa_tree_setup_routing_table()
during probe, for (N - 1) of them, &amp;#34;complete&amp;#34; will return false and they
will exit probing early. The Nth switch will set up the whole tree on
their behalf.&lt;/p&gt;
&lt;p&gt;The implication is that for (N - 1) switches, the driver binds to the
device successfully, without doing anything. When the driver is bound,
the -&amp;gt;shutdown() method may run. But if the Nth switch has failed to
initialize the tree, there is nothing to do for the (N - 1) driver
instances, since the slave devices have not been created, etc. Moreover,
dsa_switch_shutdown() expects that the calling @ds has been in fact
initialized, so it jumps at dereferencing the various data structures,
which is incorrect.&lt;/p&gt;
&lt;p&gt;Avoid the ensuing NULL pointer dereferences by simply checking whether
the Nth switch has previously set &amp;#34;ds-&amp;gt;setup = true&amp;#34; for the switch
which is currently shutting down. The entire setup is serialized under
dsa2_mutex which we already hold.&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;net: dsa: fix panic on shutdown if multi-chip tree failed to probe&lt;/p&gt;
&lt;p&gt;DSA probing is atypical because a tree of devices must probe all at
once, so out of N switches which call dsa_tree_setup_routing_table()
during probe, for (N - 1) of them, &amp;#34;complete&amp;#34; will return false and they
will exit probing early. The Nth switch will set up the whole tree on
their behalf.&lt;/p&gt;
&lt;p&gt;The implication is that for (N - 1) switches, the driver binds to the
device successfully, without doing anything. When the driver is bound,
the -&amp;gt;shutdown() method may run. But if the Nth switch has failed to
initialize the tree, there is nothing to do for the (N - 1) driver
instances, since the slave devices have not been created, etc. Moreover,
dsa_switch_shutdown() expects that the calling @ds has been in fact
initialized, so it jumps at dereferencing the various data structures,
which is incorrect.&lt;/p&gt;
&lt;p&gt;Avoid the ensuing NULL pointer dereferences by simply checking whether
the Nth switch has previously set &amp;#34;ds-&amp;gt;setup = true&amp;#34; for the switch
which is currently shutting down. The entire setup is serialized under
dsa2_mutex which we already hold.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49195</guid>
    </item>
  </channel>
</rss>
