<?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://db.gcve.eu</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>Fri, 30 Oct 2026 00:40:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99117 — net: bridge: mcast: don't truncate the port group walk on teardown</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99117</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: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;gt;mglist with hlist_for_each_entry_safe(). However,
br_multicast_find_del_pg() can also delete other entries from the same
list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;gt;next and terminates the walk early. The reproducer triggers
this in both teardown walks, leaving port groups in the bridge mdb with
a dangling -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320
   __mdb_fill_info+0x1191/0x1320
   br_mdb_dump+0x594/0xe40
   rtnl_mdb_dump+0x1cf/0x5d0&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;gt;multicast_lock. The GC worker must acquire the same lock before
detaching the group for destruction, so the node remains alive while
the walk uses the preserved pointer.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;gt;next means a walk can now reach a group that an earlier
iteration already deleted as a side effect. That group is off mp-&amp;gt;ports,
so br_multicast_find_del_pg() would fall through its port scan and hit
the trailing WARN_ON(1). Skip such groups at the top of that helper: a
port group is put on port-&amp;gt;mglist when it is created and only unlinked
when it is delete…&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: mcast: don&amp;#39;t truncate the port group walk on teardown&lt;/p&gt;
&lt;p&gt;__br_multicast_disable_port_ctx() and br_multicast_del_port() walk
port-&amp;gt;mglist with hlist_for_each_entry_safe(). However,
br_multicast_find_del_pg() can also delete other entries from the same
list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().&lt;/p&gt;
&lt;p&gt;If such an entry is the iterator&amp;#39;s saved next node, hlist_del_init()
clears its -&amp;gt;next and terminates the walk early. The reproducer triggers
this in both teardown walks, leaving port groups in the bridge mdb with
a dangling -&amp;gt;key.port after del_nbp() frees the port:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320
   __mdb_fill_info+0x1191/0x1320
   br_mdb_dump+0x594/0xe40
   rtnl_mdb_dump+0x1cf/0x5d0&lt;/p&gt;
&lt;p&gt;Use hlist_del_init_rcu() to unlink the group while preserving -&amp;gt;next.
br_multicast_del_pg() and the teardown walks run under
br-&amp;gt;multicast_lock. The GC worker must acquire the same lock before
detaching the group for destruction, so the node remains alive while
the walk uses the preserved pointer.&lt;/p&gt;
&lt;p&gt;Preserving -&amp;gt;next means a walk can now reach a group that an earlier
iteration already deleted as a side effect. That group is off mp-&amp;gt;ports,
so br_multicast_find_del_pg() would fall through its port scan and hit
the trailing WARN_ON(1). Skip such groups at the top of that helper: a
port group is put on port-&amp;gt;mglist when it is created and only unlinked
when it is delete…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99117</guid>
    </item>
  </channel>
</rss>
