<?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>Sat, 03 Oct 2026 20:54:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48814 — net: dsa: seville: register the mdiobus under devres</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48814</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: seville: register the mdiobus under devres&lt;/p&gt;
&lt;p&gt;As explained in commits:
74b6d7d13307 (&amp;#34;net: dsa: realtek: register the MDIO bus under devres&amp;#34;)
5135e96a3dd2 (&amp;#34;net: dsa: don&amp;#39;t allocate the slave_mii_bus using devres&amp;#34;)&lt;/p&gt;
&lt;p&gt;mdiobus_free() will panic when called from devm_mdiobus_free() &amp;lt;-
devres_release_all() &amp;lt;- __device_release_driver(), and that mdiobus was
not previously unregistered.&lt;/p&gt;
&lt;p&gt;The Seville VSC9959 switch is a platform device, so the initial set of
constraints that I thought would cause this (I2C or SPI buses which call
-&amp;gt;remove on -&amp;gt;shutdown) do not apply. But there is one more which
applies here.&lt;/p&gt;
&lt;p&gt;If the DSA master itself is on a bus that calls -&amp;gt;remove from -&amp;gt;shutdown
(like dpaa2-eth, which is on the fsl-mc bus), there is a device link
between the switch and the DSA master, and device_links_unbind_consumers()
will unbind the seville switch driver on shutdown.&lt;/p&gt;
&lt;p&gt;So the same treatment must be applied to all DSA switch drivers, which
is: either use devres for both the mdiobus allocation and registration,
or don&amp;#39;t use devres at all.&lt;/p&gt;
&lt;p&gt;The seville driver has a code structure that could accommodate both the
mdiobus_unregister and mdiobus_free calls, but it has an external
dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls
devm_mdiobus_alloc_size() on its behalf. So rather than restructuring
that, and exporting yet one more symbol mscc_miim_teardown(), let&amp;#39;s work
with devres and replac…&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: seville: register the mdiobus under devres&lt;/p&gt;
&lt;p&gt;As explained in commits:
74b6d7d13307 (&amp;#34;net: dsa: realtek: register the MDIO bus under devres&amp;#34;)
5135e96a3dd2 (&amp;#34;net: dsa: don&amp;#39;t allocate the slave_mii_bus using devres&amp;#34;)&lt;/p&gt;
&lt;p&gt;mdiobus_free() will panic when called from devm_mdiobus_free() &amp;lt;-
devres_release_all() &amp;lt;- __device_release_driver(), and that mdiobus was
not previously unregistered.&lt;/p&gt;
&lt;p&gt;The Seville VSC9959 switch is a platform device, so the initial set of
constraints that I thought would cause this (I2C or SPI buses which call
-&amp;gt;remove on -&amp;gt;shutdown) do not apply. But there is one more which
applies here.&lt;/p&gt;
&lt;p&gt;If the DSA master itself is on a bus that calls -&amp;gt;remove from -&amp;gt;shutdown
(like dpaa2-eth, which is on the fsl-mc bus), there is a device link
between the switch and the DSA master, and device_links_unbind_consumers()
will unbind the seville switch driver on shutdown.&lt;/p&gt;
&lt;p&gt;So the same treatment must be applied to all DSA switch drivers, which
is: either use devres for both the mdiobus allocation and registration,
or don&amp;#39;t use devres at all.&lt;/p&gt;
&lt;p&gt;The seville driver has a code structure that could accommodate both the
mdiobus_unregister and mdiobus_free calls, but it has an external
dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls
devm_mdiobus_alloc_size() on its behalf. So rather than restructuring
that, and exporting yet one more symbol mscc_miim_teardown(), let&amp;#39;s work
with devres and replac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48814</guid>
    </item>
  </channel>
</rss>
