Skip to main content

Linux Kernel CVE-2026-72389

| EUVDEUVD-2026-59288 HIGH
2026-08-15 Linux GHSA-7jq5-5rp7-v6gf
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.0 HIGH

AC:H assigned because exploitation requires deliberately engineering a specific timer-armed admin-down state before bridge deletion; PR:L reflects user-namespace CAP_NET_ADMIN; full C/I/A from kernel UAF code execution.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/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
Aug 17, 2026 - 09:00 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:56 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 05:56 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

bridge: stp: Fix a potential use-after-free when deleting a bridge

The three STP timers are not supposed to be armed while the bridge is administratively down. They are synchronously deactivated when the bridge is put administratively down and the various call sites check for 'IFF_UP' before arming them.

This check is missing from br_topology_change_detection() and it is possible to engineer a situation in which the topology change timer is armed while the bridge is administratively down, resulting in a use-after-free [1] when the bridge is deleted.

Fix by adding the missing check and for good measures synchronously shutdown the three timers when the bridge is deleted.

[1] ODEBUG: free active (active state 0) object: ffff88811662b9b0 object type: timer_list hint: br_topology_change_timer_expired (net/bridge/br_stp_timer.c:120) WARNING: lib/debugobjects.c:629 at debug_print_object+0x1bc/0x450, CPU#9: ip/359

AnalysisAI

Use-after-free in the Linux kernel bridge STP subsystem allows a local low-privileged attacker to achieve kernel code execution by engineering a specific state involving the topology change timer. The flaw exists in br_topology_change_detection(), which lacks the IFF_UP guard present at all other STP timer-arming call sites, enabling the timer to be armed while the bridge is administratively down; deleting the bridge subsequently frees kernel structures while the timer remains scheduled, triggering a dereference of freed memory when the timer fires. No public exploit is identified and EPSS sits at 0.21% (12th percentile), though the CVSS 7.8 High score with full C/I/A impact correctly reflects the severity of kernel-level UAF if successfully triggered.

Technical ContextAI

The Linux kernel's network bridge subsystem implements IEEE 802.1D Spanning Tree Protocol via net/bridge/br_stp_timer.c. Three STP timers exist - hello, forward-delay, and topology-change - and all are supposed to be inert when a bridge interface is administratively down (IFF_UP cleared). Other call sites that arm these timers check IFF_UP before proceeding; br_topology_change_detection() was the single omission. An attacker who manipulates bridge lifecycle (admin-down then delete) while the topology change timer is armed causes the kernel to free the bridge's associated structures while the timer remains in the scheduler queue. When the timer fires (br_topology_change_timer_expired at br_stp_timer.c:120), it accesses the already-freed timer_list object at address ffff88811662b9b0, as captured in the DEBUGOBJECTS warning: 'free active (active state 0) object … type: timer_list'. This maps to CWE-416 (Use After Free), though no formal CWE is assigned in the NVD entry. The fix adds the missing IFF_UP check and synchronously deactivates all three timers at bridge deletion time. CPE: cpe:2.3:a:linux:linux:*.

RemediationAI

The primary fix is upgrading to a patched kernel: 5.15.212 or later for the 5.15.x LTS branch, 6.1.178 or later for 6.1.x LTS, 6.6.145 or later for 6.6.x LTS, 6.12.97 or later for 6.12.x, 6.18.40 or later for 6.18.x, 7.1.5 or later for 7.1.x, or 7.2-rc2 or later for mainline pre-release; patch commits are indexed at https://git.kernel.org/stable/c/c86579b0a2d201792bcb59316629f4ba4758cfc8 and the six sibling commits in the references. For systems where immediate patching is not feasible, three compensating controls exist with distinct trade-offs: (1) disable unprivileged user namespaces via sysctl kernel.unprivileged_userns_clone=0 (blocks container-based exploitation paths but breaks rootless container workloads); (2) unload or blacklist the bridge kernel module (modprobe -r bridge) where bridged networking is not required, eliminating the attack surface entirely at the cost of bridge functionality; (3) apply seccomp or AppArmor/SELinux policy to restrict network bridge syscalls for untrusted workloads, which reduces risk without breaking legitimate bridging but requires per-workload policy management. NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-72389.

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

CVE-2026-72389 vulnerability details – vuln.today

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