CVE-2026-72389

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c86579b0a2d201792bcb59316629f4ba4758cfc8
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b4b3458ef88df4798632619f018791d4344bcd92
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c40eec06eeac37c58e47a6058eb32901218d5d4
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40cbfa3a28e0919469d1b086629bb3ce38a83593
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39283907a25e5caf0f2bd2947f6e56644b01e2b7
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a00517db8de4be7df3d483b215c5544fb30a191
generic

bridge: stp: Fix a potential use-after-free when deleting a bridge - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/297a747f59bff6573196d7236178144d66524e68

Vendor Advisories for CVE-2026-72389(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 30× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:19 UTCGHSA enrichment
  2. 2026-08-20 11:23 UTCGHSA enrichment
  3. 2026-08-20 00:27 UTCEG score recompute
  4. 2026-08-20 00:27 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 13:31 UTCGHSA enrichment
  7. 2026-08-19 02:35 UTCGHSA enrichment
  8. 2026-08-18 15:35 UTCEG score recompute
  9. 2026-08-18 15:35 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 04:24 UTCGHSA enrichment
  13. 2026-08-17 17:28 UTCEG score recompute
  14. 2026-08-17 17:28 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:29 UTCEG score recompute
  17. 2026-08-17 06:29 UTCGHSA enrichment
  18. 2026-08-17 05:57 UTCEG score recompute▲ 7.80
  19. 2026-08-17 05:57 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-08-17 05:29 UTCEG score recompute
  22. 2026-08-17 05:29 UTCGHSA enrichment
  23. 2026-08-17 05:24 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 5 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 06:35 UTCGHSA enrichment
  3. 2026-08-15 06:23 UTCNVD update
  4. 2026-08-15 06:05 UTCEG score recompute
  5. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72389?
CVE-2026-72389 is a high vulnerability published on August 15, 2026. 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…
When was CVE-2026-72389 disclosed?
CVE-2026-72389 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72389 actively exploited?
CVE-2026-72389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72389?
CVE-2026-72389 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72389, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72389

Explore →

Is Your Infrastructure Affected by CVE-2026-72389?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs