<?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>Thu, 01 Oct 2026 15:30:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72411 — net: dsa: mxl862xx: fix use-after-free of DSA ports in crc_err_work</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72411</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: mxl862xx: fix use-after-free of DSA ports in crc_err_work&lt;/p&gt;
&lt;p&gt;Upon an MDIO CRC error mxl862xx_crc_err_work_fn() walks the DSA ports
and closes the CPU port conduits:&lt;/p&gt;
&lt;p&gt;dsa_switch_for_each_cpu_port(dp, priv-&amp;gt;ds)
		dev_close(dp-&amp;gt;conduit);&lt;/p&gt;
&lt;p&gt;mxl862xx_remove() unregisters the switch before cancelling this work:&lt;/p&gt;
&lt;p&gt;set_bit(MXL862XX_FLAG_WORK_STOPPED, &amp;amp;priv-&amp;gt;flags);
	cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_work);
	dsa_unregister_switch(ds);
	mxl862xx_host_shutdown(priv);&lt;/p&gt;
&lt;p&gt;dsa_unregister_switch() frees the dsa_port objects. If a CRC error
schedules the work during teardown it can run after the ports have been
freed and dereference freed memory.&lt;/p&gt;
&lt;p&gt;Guard the port walk with MXL862XX_FLAG_WORK_STOPPED, which is already set
before dsa_unregister_switch(). DSA tears the ports down under
rtnl_lock(), so checking the flag under rtnl_lock() means the work either
runs before teardown and sees valid ports, or runs afterwards, observes
the flag and skips the walk. This mirrors the host_flood_work handler,
which skips torn-down ports under rtnl_lock().&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: mxl862xx: fix use-after-free of DSA ports in crc_err_work&lt;/p&gt;
&lt;p&gt;Upon an MDIO CRC error mxl862xx_crc_err_work_fn() walks the DSA ports
and closes the CPU port conduits:&lt;/p&gt;
&lt;p&gt;dsa_switch_for_each_cpu_port(dp, priv-&amp;gt;ds)
		dev_close(dp-&amp;gt;conduit);&lt;/p&gt;
&lt;p&gt;mxl862xx_remove() unregisters the switch before cancelling this work:&lt;/p&gt;
&lt;p&gt;set_bit(MXL862XX_FLAG_WORK_STOPPED, &amp;amp;priv-&amp;gt;flags);
	cancel_delayed_work_sync(&amp;amp;priv-&amp;gt;stats_work);
	dsa_unregister_switch(ds);
	mxl862xx_host_shutdown(priv);&lt;/p&gt;
&lt;p&gt;dsa_unregister_switch() frees the dsa_port objects. If a CRC error
schedules the work during teardown it can run after the ports have been
freed and dereference freed memory.&lt;/p&gt;
&lt;p&gt;Guard the port walk with MXL862XX_FLAG_WORK_STOPPED, which is already set
before dsa_unregister_switch(). DSA tears the ports down under
rtnl_lock(), so checking the flag under rtnl_lock() means the work either
runs before teardown and sees valid ports, or runs afterwards, observes
the flag and skips the walk. This mirrors the host_flood_work handler,
which skips torn-down ports under rtnl_lock().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72411</guid>
    </item>
  </channel>
</rss>
