CVE-2026-72239

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:

x86/virt/sev: Revert "Drop WBINVD before setting MSR_AMD64_SYSCFG_SNP_EN"

Revert

99cf1fb58e68 ("x86/virt/sev: Drop WBINVD before setting MSR_AMD64_SYSCFG_SNP_EN").

Section 8.8 of the SNP spec says:

Before invoking SNP_INIT_EX with INIT_RMP set to 1, software must ensure that no CPUs contain dirty cache lines for the memory containing the RMP.

Cachelines can be moved from cache to cache in a dirty state. The wbinvd_on_all_cpus() before SNP_INIT_EX flushes the caches for each CPU, but if the IPIs for WBINVD race with this dirty cacheline movement, it is possible that they may not get flushed, violating the firmware requirement.

Doing wbinvd_on_all_cpus() before setting SNPEn is safer since the RMP table is not yet in use.

[ Heroically bisected by Srikanth. ] [ bp: Massage commit message. ]

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

x86/virt/sev: Revert "Drop WBINVD before setting MSR_AMD64_SYSCFG_SNP_EN" - kernel/git/stable/linux.git - Linux kernel stable tree

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

x86/virt/sev: Revert "Drop WBINVD before setting MSR_AMD64_SYSCFG_SNP_EN" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c2509f3b79756679a02bea649c6a7501b58f52c

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

Frequently asked(5)

What is CVE-2026-72239?
CVE-2026-72239 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: x86/virt/sev: Revert "Drop WBINVD before setting MSRAMD64SYSCFGSNPEN" Revert 99cf1fb58e68 ("x86/virt/sev: Drop WBINVD before setting MSRAMD64SYSCFGSNPEN"). Section 8.8 of the SNP spec says: Before invoking SNPINITEX with INIT_RMP…
When was CVE-2026-72239 disclosed?
CVE-2026-72239 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-72239 actively exploited?
CVE-2026-72239 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-72239?
CVE-2026-72239 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-72239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72239, 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-72239

Explore →

Is Your Infrastructure Affected by CVE-2026-72239?

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

Start Free Scan →Browse All CVEs