CVE-2026-64032bridge: mcast: Fix a possible use-after-free when removing a bridge port
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bridge: mcast: Fix a possible use-after-free when removing a bridge port When per-VLAN multicast snooping is enabled, the bridge iterates over all the bridge ports, disables the per-port multicast context on each port and enables the per-{port, VLAN} multicast contexts instead. The reverse happens when per-VLAN multicast snooping is disabled. When global multicast snooping is enabled, the bridge iterates over all the bridge ports and enables the per-port multicast context on each port. The reverse happens when multicast snooping is disabled. The above scheme can result in a situation where both types of contexts (per-port and per-{port, VLAN}) are enabled on a single bridge port: # ip link add name br1 up type bridge mcast_snooping 1 mcast_querier 1 vlan_filtering 1 # ip link add name dummy1 up master br1 type dummy # ip link set dev br1 type bridge mcast_vlan_snooping 1 # ip link set dev br1 type bridge mcast_snooping 0 # ip link set dev br1 type bridge mcast_snooping 1 This is not intended and it is a problem since the commit cited below. Prior to this commit, when removing a bridge port, br_multicast_disable_port() would disable the per-port multicast context and the per-{port, VLAN} multicast contexts would get disabled when flushing VLANs. After this commit, br_multicast_disable_port() only disables the per-port multicast context if per-VLAN multicast snooping is disabled. If both types of contexts were enabled on the port when it was removed, the per-port multicast context would remain enabled when freeing the bridge port, leading to a use-after-free [1]. Fix by preventing the bridge from enabling / disabling the per-port multicast contexts when toggling global multicast snooping if per-VLAN multicast snooping is enabled. [1] ODEBUG: free active (active state 0) object: ffff88810f8bda78 object type: timer_list hint: br_ip6_multicast_port_query_expired (net/bridge/br_multicast.c:1927) WARNING: lib/debugobjects.c:629 at debug_print_object+0x1b1/0x3e0, CPU#5: swapper/5/0 [...] Call Trace: <IRQ> __debug_check_no_obj_freed (lib/debugobjects.c:1116) kfree (mm/slub.c:2620 mm/slub.c:6250 mm/slub.c:6565) kobject_cleanup (lib/kobject.c:689) rcu_do_batch (kernel/rcu/tree.c:2617) rcu_core (kernel/rcu/tree.c:2869) handle_softirqs (kernel/softirq.c:622) __irq_exit_rcu (kernel/softirq.c:656 kernel/softirq.c:496 kernel/softirq.c:735) irq_exit_rcu (kernel/softirq.c:752) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1061 (discriminator 47) arch/x86/kernel/apic/apic.c:1061 (discriminator 47)) </IRQ>
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 410a033bfa8c7daefbae0225c836693db2149ec1 – < ddefd1b8e5eb58933a697ab38334f0fd82e7fb8b
- affected c6d16eab122744df698f18b47cf771945cd55066 – < ed3b69e60385a03df11c6d12e5d7bdf0f4a11b70
- affected b4c83b37490d61cfdd62a2b29e98a9b89004b5c0 – < 1900ca8acb92fbea8bf9abef9927c7fed03db7fc
- affected 78f768e36c065ca3f88272fcf39014782c2d4ecd – < ebe5561154c823b323bd06e350b55e0b8604d851
- affected 4b30ae9adb047dd0a7982975ec3933c529537026 – < a9224862d597d0eed0a34bbb27343f703fc4113f
- affected 4b30ae9adb047dd0a7982975ec3933c529537026 – < 7213256c91ed778a0997c2029c152b18dc50e4fd
- affected 4b30ae9adb047dd0a7982975ec3933c529537026 – < 4df78ff02629c7729168f0696a7a2123c389818d
- affected c996e25df0b3282c724bb5aca434518bc08cd963
- affected 5.15.186 – < 5.15.209
- affected 6.1.142 – < 6.1.175
- affected 6.6.95 – < 6.6.142
- affected 6.12.35 – < 6.12.92
- affected 6.15.4 – < 6.16
- affected 6.16
- unaffected < 6.16
- unaffected 5.15.209 – ≤ 5.15.*
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.142 – ≤ 6.6.*
- unaffected 6.12.92 – ≤ 6.12.*
- unaffected 6.18.34 – ≤ 6.18.*
- unaffected 7.0.11 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/ddefd1b8e5eb58933a697ab38334f0fd82e7fb8b (opens in a new tab)
- https://git.kernel.org/stable/c/ed3b69e60385a03df11c6d12e5d7bdf0f4a11b70 (opens in a new tab)
- https://git.kernel.org/stable/c/1900ca8acb92fbea8bf9abef9927c7fed03db7fc (opens in a new tab)
- https://git.kernel.org/stable/c/ebe5561154c823b323bd06e350b55e0b8604d851 (opens in a new tab)
- https://git.kernel.org/stable/c/a9224862d597d0eed0a34bbb27343f703fc4113f (opens in a new tab)
- https://git.kernel.org/stable/c/7213256c91ed778a0997c2029c152b18dc50e4fd (opens in a new tab)
- https://git.kernel.org/stable/c/4df78ff02629c7729168f0696a7a2123c389818d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45605 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64032)Record last updated .