Look up another CVE · open CVE-2026-64032 in the interactive tracker
CVE-2026-64032
bridge: mcast: Fix a possible use-after-free when removing a bridge port
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem net/bridge. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-64032 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.176-1 | Update the kernel and reboot. Fixed in 6.1.176-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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>
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
net/bridge/br_multicast.c
- What this is
- ETHERNET BRIDGEMAINTAINERS section matched on net/bridge/ · bridge@lists.linux.dev · Maintained
- Kernel module
- bridge
Check it on the machine
grep -wE 'CONFIG_BRIDGE|CONFIG_BRIDGE_IGMP_SNOOPING' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w bridgePrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sidm
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switches
- CONFIG_BRIDGE, CONFIG_BRIDGE_IGMP_SNOOPING
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-07-19 (3 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- net/bridge
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.15.186 | 5.15.209 | ddefd1b8e5eb |
| 6.1.142 | 6.1.175 | ed3b69e60385 |
| 6.6.95 | 6.6.142 | 1900ca8acb92 |
| 6.12.35 | 6.12.92 | ebe5561154c8 |
| 6.16 | 6.18.34 | a9224862d597 |
| 6.16 | 7.0.11 | 7213256c91ed |
| 6.16 | 7.1 | 4df78ff02629 |
| 6.15.4 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The vulnerable code is reached only through local bridge administration (rtnetlink RTM_NEWLINK, bridge ioctl, or sysfs), not through processing of remote network packets. An attacker must issue `ip link`/`bridge` configuration commands to create the inconsistent multicast state and remove a bridge port.
- AC:LAttack complexity, low
- The reproducer sequence is fully attacker-controlled and deterministic; syzkaller triggered it reliably. The attacker configures the toggle sequence, removes the port, and the orphaned IGMP/MLD query timers fire on schedule without depending on uncontrollable timing or memory layout.
- PR:LPrivileges required, low
- All entry paths require CAP_NET_ADMIN in the target network namespace (rtnetlink at rtnl_newlink, br_ioctl add_del_if, sysfs bridge attributes). Unprivileged local users can obtain this capability by creating a user+network namespace (`unshare -Urn`), which is widely enabled on server and container hosts.
- UI:NUser interaction, none
- Exploitation requires no action from any other user or victim; the attacker performs the entire bridge setup, state toggling, and port removal themselves.
- S:UScope, unchanged
- Successful exploitation corrupts kernel memory within the same kernel security domain. This is a standard local kernel memory corruption issue, not a cross-boundary escape such as VM guest-to-host or IOMMU bypass.
- C:HConfidentiality impact, high
- This is a heap use-after-free on a freed net_bridge_port structure; the timer callback dereferences pmctx->port->br on freed memory. UAF on kernel slab objects enables arbitrary kernel memory reads via heap grooming and reclamation of the freed port object.
- I:HIntegrity impact, high
- The UAF occurs in a timer softirq handler that reads and writes through fields of the freed port multicast context, including sending queries via br_multicast_send_query. Kernel heap UAF is exploitable for arbitrary write and control-flow hijack primitives, not merely a crash.
- A:HAvailability impact, high
- The freed port structure is kfree'd while IGMP/MLD own-query timers remain active, producing a debugobjects "free active timer" warning and use-after-free in softirq. This reliably causes kernel oops/panic and can be triggered repeatedly to deny service on shared infrastructure such as cloud hosts or software switches.