<?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 15:08:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39773 — net: bridge: fix soft lockup in br_multicast_query_expired()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39773</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&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 soft lockup in br_multicast_query_expired()&lt;/p&gt;
&lt;p&gt;When set multicast_query_interval to a large value, the local variable
&amp;#39;time&amp;#39; in br_multicast_send_query() may overflow. If the time is smaller
than jiffies, the timer will expire immediately, and then call mod_timer()
again, which creates a loop and may trigger the following soft lockup
issue.&lt;/p&gt;
&lt;p&gt;watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66]
  CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none)
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __netdev_alloc_skb+0x2e/0x3a0
   br_ip6_multicast_alloc_query+0x212/0x1b70
   __br_multicast_send_query+0x376/0xac0
   br_multicast_send_query+0x299/0x510
   br_multicast_query_expired.constprop.0+0x16d/0x1b0
   call_timer_fn+0x3b/0x2a0
   __run_timers+0x619/0x950
   run_timer_softirq+0x11c/0x220
   handle_softirqs+0x18e/0x560
   __irq_exit_rcu+0x158/0x1a0
   sysvec_apic_timer_interrupt+0x76/0x90
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;This issue can be reproduced with:
  ip link add br0 type bridge
  echo 1 &amp;gt; /sys/class/net/br0/bridge/multicast_querier
  echo 0xffffffffffffffff &amp;gt;
  	/sys/class/net/br0/bridge/multicast_query_interval
  ip link set dev br0 up&lt;/p&gt;
&lt;p&gt;The multicast_startup_query_interval can also cause this issue. Similar to
the commit 99b40610956a (&amp;#34;net: bridge: mcast: add and enforce query
interval minimum&amp;#34;), add check for the query interval maximum to fix this
issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&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 soft lockup in br_multicast_query_expired()&lt;/p&gt;
&lt;p&gt;When set multicast_query_interval to a large value, the local variable
&amp;#39;time&amp;#39; in br_multicast_send_query() may overflow. If the time is smaller
than jiffies, the timer will expire immediately, and then call mod_timer()
again, which creates a loop and may trigger the following soft lockup
issue.&lt;/p&gt;
&lt;p&gt;watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66]
  CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none)
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __netdev_alloc_skb+0x2e/0x3a0
   br_ip6_multicast_alloc_query+0x212/0x1b70
   __br_multicast_send_query+0x376/0xac0
   br_multicast_send_query+0x299/0x510
   br_multicast_query_expired.constprop.0+0x16d/0x1b0
   call_timer_fn+0x3b/0x2a0
   __run_timers+0x619/0x950
   run_timer_softirq+0x11c/0x220
   handle_softirqs+0x18e/0x560
   __irq_exit_rcu+0x158/0x1a0
   sysvec_apic_timer_interrupt+0x76/0x90
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;This issue can be reproduced with:
  ip link add br0 type bridge
  echo 1 &amp;gt; /sys/class/net/br0/bridge/multicast_querier
  echo 0xffffffffffffffff &amp;gt;
  	/sys/class/net/br0/bridge/multicast_query_interval
  ip link set dev br0 up&lt;/p&gt;
&lt;p&gt;The multicast_startup_query_interval can also cause this issue. Similar to
the commit 99b40610956a (&amp;#34;net: bridge: mcast: add and enforce query
interval minimum&amp;#34;), add check for the query interval maximum to fix this
issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39773</guid>
    </item>
  </channel>
</rss>
