VDB

CVE-2025-39773

CVE-2025-39773 PUBLISHED

net: bridge: fix soft lockup in br_multicast_query_expired()

Reported by linux · Published September 11, 2025

In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' 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. 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: <IRQ> __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 </IRQ> This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-tools-develAmazon Linux4.14.355-280.706.amzn2

Affected products

VendorProductVersions
LinuxLinuxd902eee43f1951b358d7347d9165c6af21cf7b1b, d902eee43f1951b358d7347d9165c6af21cf7b1b, d902eee43f1951b358d7347d9165c6af21cf7b1b
LinuxLinux2.6.34, 0, 5.15.190
amazon:2kernel-tools-devel0
linuxlinux_kernel2.6.34, 2.6.34, 2.6.34
amazon:2023kernel-libbpf-static0
amazon:2python-perf0
amazon:2023kernel-modules-extra-common0
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP3.1.7, 3.1.6, 3.1.5
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel-modules-extra0
amazon:2023kernel-devel0
amazon:2023kernel6.120
amazon:2023kernel0
amazon:2023kernel6.12-tools-devel0
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)3.1.5, 3.1.7, 3.1.6
amazon:2023kernel-tools0
amazon:2kernel-devel0
amazon:2023kernel6.12-tools0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-livepatch-6.12.46-66.1210

…and 29 more

Timeline

  • Sep 11, 2025 CVE Published
  • Sep 12, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 12, 2025 PoC Published (11 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (194 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (207 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score
  • Oct 29, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-39773
vulnetix vdb fixes CVE-2025-39773

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-39773/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›