Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 297a747f59bff6573196d7236178144d66524e68, 2a00517db8de4be7df3d483b215c5544fb30a191, 39283907a25e5caf0f2bd2947f6e56644b01e2b7.

Low priority for now. Upgrade to Linux Linux 297a747f59bff6573196d7236178144d66524e68, 2a00517db8de4be7df3d483b215c5544fb30a191, 39283907a25e5caf0f2bd2947f6e56644b01e2b7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72389

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c86579b0a2d201792bcb59316629f4ba4758cfc8affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 297a747f59bff6573196d7236178144d66524e68affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4c40eec06eeac37c58e47a6058eb32901218d5d4affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 39283907a25e5caf0f2bd2947f6e56644b01e2b7affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b4b3458ef88df4798632619f018791d4344bcd92affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 40cbfa3a28e0919469d1b086629bb3ce38a83593affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2a00517db8de4be7df3d483b215c5544fb30a191affected · git
    • before 2.6.12not affected · semver
    • 5.15.212 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-docsbefore 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.220.13.0.101-108.220.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.220.13.0.101-108.220.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72383Aug 15, 2026 · sctp: fix addr_wq_timer race in sctp_free_addr_wq()
    31Monitor
  • ← EarlierCVE-2026-72388Aug 15, 2026 · drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock
    0Monitor
  • Later →CVE-2026-72390Aug 15, 2026 · net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux297a747f59bff6573196d7236178144d66524e68Vendor (CNA)
Linux Linux2a00517db8de4be7df3d483b215c5544fb30a191Vendor (CNA)
Linux Linux39283907a25e5caf0f2bd2947f6e56644b01e2b7Vendor (CNA)
Linux Linux40cbfa3a28e0919469d1b086629bb3ce38a83593Vendor (CNA)
Linux Linux4c40eec06eeac37c58e47a6058eb32901218d5d4Vendor (CNA)
Linux Linuxb4b3458ef88df4798632619f018791d4344bcd92Vendor (CNA)
Linux Linuxc86579b0a2d201792bcb59316629f4ba4758cfc8Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
suse:kernel-default3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-docs3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-source3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.220.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records