Vulnerability · CVE-2026-64032
bridge: mcast: Fix a possible use-after-free when removing a bridge port
Published Jul 19, 2026 · catalog updated Oct 21, 2026 · bridge: mcast: Fix a
Check if you run it
No confirmed exploitation is on record for CVE-2026-64032. EPSS is 0.13%. Act only if a listed version of bridge: mcast: Fix a is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (bridge: mcast: Fix a).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Advisory link
- Affected products
- Linux Kernel
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:
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel0 → 5.15.209; 5.16.0 → 6.1.175; 6.2.0 → 6.6.142
How to fix CVE-2026-64032
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-64032. EPSS is 0.13%. Act only if a listed version of bridge: mcast: Fix a is installed.
Which versions are affected?
Compare what you have installed with Kernel 0 → 5.15.209; 5.16.0 → 6.1.175; 6.2.0 → 6.6.142. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jul 19, 2026 · OpenSSF OSV / OSV Scanner
Detected
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
Oct 21, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.15.209; Kernel fixed in 6.1.175; Kernel fixed in 6.6.142; Kernel fixed in 6.12.92
Oct 21, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.15.209; 5.16.0
Oct 21, 2026 · OpenSSF OSV / OSV Scanner
Updated
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
Sources
- CVE.orgVulnerability recordCVE-2026-64032
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-64032
30-day exploitation probability 0.13%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-64032
bridge: mcast: Fix a possible use-after-free when removing a bridge port
osv.dev
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.