<?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, 28 Sep 2026 14:09:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40297 — net: bridge: fix use-after-free due to MST port state bypass</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40297</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: bridge: fix use-after-free due to MST port state bypass&lt;/p&gt;
&lt;p&gt;syzbot reported[1] a use-after-free when deleting an expired fdb. It is
due to a race condition between learning still happening and a port being
deleted, after all its fdbs have been flushed. The port&amp;#39;s state has been
toggled to disabled so no learning should happen at that time, but if we
have MST enabled, it will bypass the port&amp;#39;s state, that together with VLAN
filtering disabled can lead to fdb learning at a time when it shouldn&amp;#39;t
happen while the port is being deleted. VLAN filtering must be disabled
because we flush the port VLANs when it&amp;#39;s being deleted which will stop
learning. This fix adds a check for the port&amp;#39;s vlan group which is
initialized to NULL when the port is getting deleted, that avoids the port
state bypass. When MST is enabled there would be a minimal new overhead
in the fast-path because the port&amp;#39;s vlan group pointer is cache-hot.&lt;/p&gt;
&lt;p&gt;[1] https://syzkaller.appspot.com/bug?extid=dd280197f0f7ab3917be&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: bridge: fix use-after-free due to MST port state bypass&lt;/p&gt;
&lt;p&gt;syzbot reported[1] a use-after-free when deleting an expired fdb. It is
due to a race condition between learning still happening and a port being
deleted, after all its fdbs have been flushed. The port&amp;#39;s state has been
toggled to disabled so no learning should happen at that time, but if we
have MST enabled, it will bypass the port&amp;#39;s state, that together with VLAN
filtering disabled can lead to fdb learning at a time when it shouldn&amp;#39;t
happen while the port is being deleted. VLAN filtering must be disabled
because we flush the port VLANs when it&amp;#39;s being deleted which will stop
learning. This fix adds a check for the port&amp;#39;s vlan group which is
initialized to NULL when the port is getting deleted, that avoids the port
state bypass. When MST is enabled there would be a minimal new overhead
in the fast-path because the port&amp;#39;s vlan group pointer is cache-hot.&lt;/p&gt;
&lt;p&gt;[1] https://syzkaller.appspot.com/bug?extid=dd280197f0f7ab3917be&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40297</guid>
    </item>
  </channel>
</rss>
