CVE-2026-64562

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.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:

KVM: nVMX: Hide shadow VMCS right after VMCLEAR

free_nested() frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loaded_vmcs_clear(), the vCPU might migrate before the pointer is cleared and __loaded_vmcs_clear() may then execute VMCLEAR.

The VMCS needs to stay attached until its explicit VMCLEAR completes, but then it can be hidden and the page safely freed.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

KVM: nVMX: Hide shadow VMCS right after VMCLEAR - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nVMX: Hide shadow VMCS right after VMCLEAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8001d2ce9d9bd09118ce523aef595aa094573ae3
generic

KVM: nVMX: Hide shadow VMCS right after VMCLEAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/622ebfac01ba4f9c0060cebd41257fe46fc4a0b3
generic

KVM: nVMX: Hide shadow VMCS right after VMCLEAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/589419470030a89f16cf19300658b6dc644ca946
generic

KVM: nVMX: Hide shadow VMCS right after VMCLEAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1dabef6e206568bf9d9ade74f6e56a48ea35695d

Vendor Advisories for CVE-2026-64562(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.6-1—

Data Freshness Timeline

(refreshed 41× in last 7d / 79× 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:55 UTCEPSS rescore
  2. 2026-08-20 19:21 UTCVendor advisory
  3. 2026-08-20 19:21 UTCGHSA enrichment
  4. 2026-08-20 06:24 UTCGHSA enrichment
  5. 2026-08-19 17:27 UTCEG score recompute
  6. 2026-08-19 17:27 UTCVendor advisory
  7. 2026-08-19 17:27 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:56 UTCEG score recompute
  10. 2026-08-19 16:56 UTCVendor advisory
  11. 2026-08-19 16:56 UTCGHSA enrichment
  12. 2026-08-19 10:43 UTCVendor advisory
  13. 2026-08-19 10:43 UTCGHSA enrichment
  14. 2026-08-18 21:43 UTCEG score recompute
  15. 2026-08-18 21:43 UTCVendor advisory
  16. 2026-08-18 21:43 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-18 08:40 UTCGHSA enrichment
  19. 2026-08-17 19:35 UTCVendor advisory
  20. 2026-08-17 19:35 UTCGHSA enrichment
  21. 2026-08-17 05:42 UTCEG score recompute
  22. 2026-08-17 05:42 UTCVendor advisory
  23. 2026-08-17 05:42 UTCGHSA enrichment
  24. 2026-08-17 05:14 UTCEG score recompute
  25. 2026-08-17 05:14 UTCVendor advisory
Show 54 more
  1. 2026-08-17 05:14 UTCGHSA enrichment
  2. 2026-08-16 17:26 UTCEG score recompute
  3. 2026-08-16 17:26 UTCVendor advisory
  4. 2026-08-16 17:26 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 04:29 UTCEG score recompute
  7. 2026-08-16 04:29 UTCVendor advisory
  8. 2026-08-16 04:29 UTCGHSA enrichment
  9. 2026-08-15 15:33 UTCVendor advisory
  10. 2026-08-15 15:33 UTCGHSA enrichment
  11. 2026-08-15 02:36 UTCEG score recompute
  12. 2026-08-15 02:36 UTCVendor advisory
  13. 2026-08-15 02:36 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 13:40 UTCVendor advisory
  16. 2026-08-14 13:40 UTCGHSA enrichment
  17. 2026-08-14 00:43 UTCEG score recompute
  18. 2026-08-14 00:43 UTCVendor advisory
  19. 2026-08-14 00:43 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 11:46 UTCVendor advisory
  22. 2026-08-13 11:46 UTCGHSA enrichment
  23. 2026-08-12 22:49 UTCEG score recompute
  24. 2026-08-12 22:49 UTCGHSA enrichment
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-12 09:53 UTCVendor advisory
  27. 2026-08-12 09:53 UTCGHSA enrichment
  28. 2026-08-11 20:56 UTCEG score recompute
  29. 2026-08-11 20:56 UTCVendor advisory
  30. 2026-08-11 20:56 UTCGHSA enrichment
  31. 2026-08-11 07:59 UTCEG score recompute
  32. 2026-08-11 07:59 UTCVendor advisory
  33. 2026-08-11 07:59 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 19:03 UTCGHSA enrichment
  36. 2026-08-10 06:06 UTCGHSA enrichment
  37. 2026-08-09 17:09 UTCEG score recompute
  38. 2026-08-09 17:09 UTCGHSA enrichment
  39. 2026-08-09 13:47 UTCEPSS rescore
  40. 2026-08-09 04:13 UTCEG score recompute
  41. 2026-08-09 04:13 UTCGHSA enrichment
  42. 2026-08-08 16:37 UTCEPSS rescore
  43. 2026-08-08 15:17 UTCEG score recompute▲ 8.80
  44. 2026-08-08 15:17 UTCGHSA enrichment
  45. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  46. 2026-08-07 05:39 UTCEG score recompute
  47. 2026-08-07 05:39 UTCGHSA enrichment
  48. 2026-08-06 13:47 UTCEPSS rescore
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 07:17 UTCNVD update
  53. 2026-08-04 06:35 UTCEG score recompute
  54. 2026-08-04 06:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64562?
CVE-2026-64562 is a high vulnerability published on August 4, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Hide shadow VMCS right after VMCLEAR free_nested() frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loadedvmcsclear(), the vCPU might migrate before the pointer is…
When was CVE-2026-64562 disclosed?
CVE-2026-64562 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64562 actively exploited?
CVE-2026-64562 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64562?
CVE-2026-64562 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64562?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64562, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64562

Explore →

Is Your Infrastructure Affected by CVE-2026-64562?

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

Start Free Scan →Browse All CVEs