Skip to main content

Linux Kernel EUVDEUVD-2026-45605

| CVE-2026-64032 HIGH
2026-07-19 Linux GHSA-qpwr-692j-qmg9
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local-only via netlink config (AV:L), deterministic reproducer (AC:L), needs CAP_NET_ADMIN obtainable in an unprivileged netns (PR:L), no interaction (UI:N); kernel UAF gives full C/I/A impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 16:59 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:39 cve.org
HIGH 7.8
CVE Published
Jul 19, 2026 - 15:39 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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>

AnalysisAI

Use-after-free in the Linux kernel's bridge multicast (br_multicast) subsystem lets a local user with network-configuration capability crash the host or potentially execute code by toggling global multicast snooping while per-VLAN multicast snooping is enabled on a VLAN-filtering bridge. The flawed logic can leave both per-port and per-{port, VLAN} multicast contexts active simultaneously, so a per-port context (including its query timer) survives after the bridge port is freed, yielding a UAF confirmed by kernel debug tooling (ODEBUG free-active). No public exploit has been identified and EPSS is low (0.17%), but a deterministic reproducer is included in the fix, and the CVSS is 7.8 (High).

Technical ContextAI

The bug lives in net/bridge/br_multicast.c, which implements IGMP/MLD snooping for the Linux software bridge. The bridge supports two multicast context models: a per-port context and, when mcast_vlan_snooping is on, per-{port, VLAN} contexts. A regression (the commit cited in the advisory) changed br_multicast_disable_port() so it only tears down the per-port context when per-VLAN snooping is disabled. Because toggling global mcast_snooping still enables/disables per-port contexts even while per-VLAN snooping is active, both context types can end up enabled on one port. When the port is later removed and freed, the still-armed per-port context's timer (br_ip6_multicast_port_query_expired) references freed memory - a classic CWE-416 use-after-free (the input lists CWE as N/A). The CPE identifies the affected component only as cpe:2.3:a:linux:linux, i.e. the mainline/stable kernel.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 5.15.209, 6.1.175, 6.6.142, 6.12.92, 6.16, 7.0.11, 7.1, or 6.18.34 (or later) as matches your branch - via your distribution's kernel update once it ships the corresponding stable backport; the fix commits are published at git.kernel.org/stable (e.g. ddefd1b8e5eb58933a697ab38334f0fd82e7fb8b and ed3b69e60385a03df11c6d12e5d7bdf0f4a11b70). If you cannot patch immediately, the exposure requires a specific bridge configuration, so a targeted workaround is to avoid enabling per-VLAN multicast snooping (leave mcast_vlan_snooping off) on VLAN-filtering bridges, or avoid dynamically toggling mcast_snooping on such bridges - trade-off: this disables per-VLAN IGMP/MLD snooping, causing multicast to be flooded per bridge rather than pruned per VLAN. As a broader compensating control, restrict CAP_NET_ADMIN and disallow unprivileged user+network namespaces (e.g. sysctl kernel.unprivileged_userns_clone=0 where available) to prevent low-privilege local users from reaching the vulnerable configuration path - trade-off: this can break container runtimes and sandboxes that rely on unprivileged namespaces.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45605 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy