CVE-2026-72154

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:

openrisc: Fix jump_label smp syncing

The original commit 8c30b0018f9d ("openrisc: Add jump label support") copies from arm64 and does not properly consider how icache invalidation on remote cores works in OpenRISC. On OpenRISC remote icaches need to be invalidated otherwise static key's may remain state after updating.

Fix SMP cache syncing by:

  • Properly invalidate remote core icaches on SMP systems by using
icache_all_inv. The old code uses kick_all_cpus_sync() which runs a no-op IPI function call on remote CPU's which does execute a lot of code and flushes many cache lines in the process, but does not flush all and it's not correct on OpenRISC.
  • For architectures that do not have WRITETHROUGH caches be sure
to flush the dcache after patching.

To test this I first reproduced the issue using a custom test module [0]. The test confirmed that some icache lines maintained stale static_key code sequences after calling static_branch_enable(). After this patch there are no longer jump_label coherency issues.

[0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test

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
7%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

openrisc: Fix jump_label smp syncing - kernel/git/stable/linux.git - Linux kernel stable tree

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

openrisc: Fix jump_label smp syncing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57740658042daf591c57d6e700d9a304d5972552
generic

openrisc: Fix jump_label smp syncing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fac46068fe4cea22ed373432b9173a915e8e60d

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

Frequently asked(5)

What is CVE-2026-72154?
CVE-2026-72154 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: openrisc: Fix jump_label smp syncing The original commit 8c30b0018f9d ("openrisc: Add jump label support") copies from arm64 and does not properly consider how icache invalidation on remote cores works in OpenRISC. On OpenRISC…
When was CVE-2026-72154 disclosed?
CVE-2026-72154 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-72154 actively exploited?
CVE-2026-72154 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 92.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72154?
CVE-2026-72154 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72154?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72154, 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-72154

Explore →

Is Your Infrastructure Affected by CVE-2026-72154?

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

Start Free Scan →Browse All CVEs