CVE-2026-72109

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:

net: sparx5: unregister blocking notifier on init failure

sparx5_register_notifier_blocks() registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path unregisters the switchdev and netdevice notifiers, but leaves the blocking notifier registered.

Add a separate error label for the workqueue allocation failure path and unregister the switchdev blocking notifier there.

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

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a3c44a003176282ee4306b7c96e5a536c6f0707
generic

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/483be61b4a9a6df3b7cb277e8f189e082dee4cb8
generic

net: sparx5: unregister blocking notifier on init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17f113e7b622dc850992ade540181717de6a8561

Vendor Advisories for CVE-2026-72109(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 29× in last 7d / 29× 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 17:22 UTCGHSA enrichment
  2. 2026-08-20 05:52 UTCGHSA enrichment
  3. 2026-08-19 18:25 UTCEG score recompute
  4. 2026-08-19 18:25 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 05:30 UTCGHSA enrichment
  7. 2026-08-18 18:03 UTCEG score recompute
  8. 2026-08-18 18:03 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 06:28 UTCGHSA enrichment
  12. 2026-08-17 19:01 UTCEG score recompute
  13. 2026-08-17 19:01 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:21 UTCEG score recompute
  16. 2026-08-17 06:21 UTCGHSA enrichment
  17. 2026-08-17 06:00 UTCEG score recompute▲ 7.80
  18. 2026-08-17 06:00 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  20. 2026-08-17 05:33 UTCEG score recompute
  21. 2026-08-17 05:33 UTCGHSA enrichment
  22. 2026-08-17 05:24 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 4 more
  1. 2026-08-15 06:43 UTCGHSA enrichment
  2. 2026-08-15 06:23 UTCNVD update
  3. 2026-08-15 06:12 UTCEG score recompute
  4. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72109?
CVE-2026-72109 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net: sparx5: unregister blocking notifier on init failure sparx5registernotifier_blocks() registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path…
When was CVE-2026-72109 disclosed?
CVE-2026-72109 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-72109 actively exploited?
CVE-2026-72109 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72109?
CVE-2026-72109 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72109, 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-72109

Explore →

Is Your Infrastructure Affected by CVE-2026-72109?

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

Start Free Scan →Browse All CVEs