CVE-2026-72291

CRITICALPre-NVD 9.39.3
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: 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:

KVM: s390: Fix unlikely race in try_get_locked_pte()

Fix an unlikely race in try_get_locked_pte(), which could have happened if puds or pmds get unmapped between the p?dp_get() and p?d_offset() functions.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
46(Track)
EG Risk 46/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
Severity93% × 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 (2)

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

KVM: s390: Fix unlikely race in try_get_locked_pte() - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: s390: Fix unlikely race in try_get_locked_pte() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5670b7f927f8d98685f3f5873dbf9f8d7a5a63f3

Vendor Advisories for CVE-2026-72291(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 51× in last 7d / 51× 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-21 06:57 UTCGHSA enrichment
  2. 2026-08-21 03:18 UTCGHSA enrichment
  3. 2026-08-20 23:37 UTCEG score recompute
  4. 2026-08-20 23:37 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 19:59 UTCGHSA enrichment
  7. 2026-08-20 16:20 UTCGHSA enrichment
  8. 2026-08-20 12:41 UTCGHSA enrichment
  9. 2026-08-20 09:02 UTCGHSA enrichment
  10. 2026-08-20 05:24 UTCGHSA enrichment
  11. 2026-08-20 01:44 UTCGHSA enrichment
  12. 2026-08-19 22:03 UTCGHSA enrichment
  13. 2026-08-19 18:24 UTCEG score recompute
  14. 2026-08-19 18:24 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 13:15 UTCGHSA enrichment
  17. 2026-08-19 09:37 UTCGHSA enrichment
  18. 2026-08-19 05:57 UTCGHSA enrichment
  19. 2026-08-19 02:16 UTCGHSA enrichment
  20. 2026-08-18 22:36 UTCGHSA enrichment
  21. 2026-08-18 18:56 UTCGHSA enrichment
  22. 2026-08-18 15:17 UTCEG score recompute
  23. 2026-08-18 15:17 UTCGHSA enrichment
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 26 more
  1. 2026-08-18 11:37 UTCGHSA enrichment
  2. 2026-08-18 07:57 UTCGHSA enrichment
  3. 2026-08-18 04:18 UTCGHSA enrichment
  4. 2026-08-18 00:37 UTCGHSA enrichment
  5. 2026-08-17 20:56 UTCGHSA enrichment
  6. 2026-08-17 17:17 UTCEG score recompute
  7. 2026-08-17 17:16 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 13:37 UTCGHSA enrichment
  10. 2026-08-17 09:58 UTCEG score recompute
  11. 2026-08-17 09:58 UTCGHSA enrichment
  12. 2026-08-17 06:19 UTCEG score recompute
  13. 2026-08-17 06:19 UTCGHSA enrichment
  14. 2026-08-17 05:59 UTCEG score recompute 9.30
  15. 2026-08-17 05:59 UTCGHSA enrichment
  16. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
  17. 2026-08-17 05:31 UTCEG score recompute
  18. 2026-08-17 05:31 UTCGHSA enrichment
  19. 2026-08-17 05:24 UTCMITRE cvelistV5
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-15 06:38 UTCGHSA enrichment
  24. 2026-08-15 06:23 UTCNVD update
  25. 2026-08-15 06:08 UTCEG score recompute
  26. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72291?
CVE-2026-72291 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix unlikely race in trygetlocked_pte() Fix an unlikely race in trygetlocked_pte(), which could have happened if puds or pmds get unmapped between the p?dpget() and p?doffset() functions.
When was CVE-2026-72291 disclosed?
CVE-2026-72291 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-72291 actively exploited?
CVE-2026-72291 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72291?
CVE-2026-72291 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-72291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72291, 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-72291

Explore →

Is Your Infrastructure Affected by CVE-2026-72291?

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