<?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:41:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37864 — net: dsa: clean up FDB, MDB, VLAN entries on unbind</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37864</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: clean up FDB, MDB, VLAN entries on unbind&lt;/p&gt;
&lt;p&gt;As explained in many places such as commit b117e1e8a86d (&amp;#34;net: dsa:
delete dsa_legacy_fdb_add and dsa_legacy_fdb_del&amp;#34;), DSA is written given
the assumption that higher layers have balanced additions/deletions.
As such, it only makes sense to be extremely vocal when those
assumptions are violated and the driver unbinds with entries still
present.&lt;/p&gt;
&lt;p&gt;But Ido Schimmel points out a very simple situation where that is wrong:
https://lore.kernel.org/netdev/ZDazSM5UsPPjQuKr@shredder/
(also briefly discussed by me in the aforementioned commit).&lt;/p&gt;
&lt;p&gt;Basically, while the bridge bypass operations are not something that DSA
explicitly documents, and for the majority of DSA drivers this API
simply causes them to go to promiscuous mode, that isn&amp;#39;t the case for
all drivers. Some have the necessary requirements for bridge bypass
operations to do something useful - see dsa_switch_supports_uc_filtering().&lt;/p&gt;
&lt;p&gt;Although in tools/testing/selftests/net/forwarding/local_termination.sh,
we made an effort to popularize better mechanisms to manage address
filters on DSA interfaces from user space - namely macvlan for unicast,
and setsockopt(IP_ADD_MEMBERSHIP) - through mtools - for multicast, the
fact is that &amp;#39;bridge fdb add ... self static local&amp;#39; also exists as
kernel UAPI, and might be useful to someone, even if only for a quick
hack.&lt;/p&gt;
&lt;p&gt;It seems counter-productive to block that path by i…&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: clean up FDB, MDB, VLAN entries on unbind&lt;/p&gt;
&lt;p&gt;As explained in many places such as commit b117e1e8a86d (&amp;#34;net: dsa:
delete dsa_legacy_fdb_add and dsa_legacy_fdb_del&amp;#34;), DSA is written given
the assumption that higher layers have balanced additions/deletions.
As such, it only makes sense to be extremely vocal when those
assumptions are violated and the driver unbinds with entries still
present.&lt;/p&gt;
&lt;p&gt;But Ido Schimmel points out a very simple situation where that is wrong:
https://lore.kernel.org/netdev/ZDazSM5UsPPjQuKr@shredder/
(also briefly discussed by me in the aforementioned commit).&lt;/p&gt;
&lt;p&gt;Basically, while the bridge bypass operations are not something that DSA
explicitly documents, and for the majority of DSA drivers this API
simply causes them to go to promiscuous mode, that isn&amp;#39;t the case for
all drivers. Some have the necessary requirements for bridge bypass
operations to do something useful - see dsa_switch_supports_uc_filtering().&lt;/p&gt;
&lt;p&gt;Although in tools/testing/selftests/net/forwarding/local_termination.sh,
we made an effort to popularize better mechanisms to manage address
filters on DSA interfaces from user space - namely macvlan for unicast,
and setsockopt(IP_ADD_MEMBERSHIP) - through mtools - for multicast, the
fact is that &amp;#39;bridge fdb add ... self static local&amp;#39; also exists as
kernel UAPI, and might be useful to someone, even if only for a quick
hack.&lt;/p&gt;
&lt;p&gt;It seems counter-productive to block that path by i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37864</guid>
    </item>
  </channel>
</rss>
