CVE-2026-72277

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: arm64: nv: Inject SEA if guest VNCR isn't normal memory

When constructing an L1 VNCR mapping, KVM unconditionally uses cacheable memory attributes, even if the underlying PFN isn't memory. This gets particularly hairy if the endpoint doesn't support cacheable memory attributes, potentially throwing an SError on writeback...

While KVM does permit cacheable memory attributes on certain PFNMAP VMAs, kvm_translate_vncr() isn't currently grabbing the VMA. So do the simpler thing for now and just reject everything that isn't memory.

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
9%
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

KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-72277?
CVE-2026-72277 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory When constructing an L1 VNCR mapping, KVM unconditionally uses cacheable memory attributes, even if the underlying PFN isn't memory. This gets particularly hairy if the…
When was CVE-2026-72277 disclosed?
CVE-2026-72277 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-72277 actively exploited?
CVE-2026-72277 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 90.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72277?
CVE-2026-72277 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-72277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72277, 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-72277

Explore →

Is Your Infrastructure Affected by CVE-2026-72277?

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