CVE-2026-72279

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.0EG
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.0Exploit: 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: Respect read-only PFN when mapping L1 VNCR

KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backing PFN is read-only (e.g. RO memslot), meaning that the L1 VNCR should use at most a read-only mapping.

Cache the writability of the PFN in the VNCR TLB and use it to constrain the resulting fixmap permissions. Promote VNCR permission faults to an SEA in the case where the guest attempts to write to a read-only endpoint. Conveniently, this also plugs a page leak found by Sashiko [*] resulting from the early return for a read-only PFN.

CVSS v3
9.0
EG Score
9.0(high)
EG Risk
45(Track)
EG Risk 45/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
Severity90% × 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: Respect read-only PFN when mapping L1 VNCR - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c50db5bcbb9073cb2fd97be51b962de92f429e9
generic

KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2684e02bac41c5220f6c1ab2bdcc957b71812977

Vendor Advisories for CVE-2026-72279(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 46× in last 7d / 46× 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 05:58 UTCGHSA enrichment
  2. 2026-08-21 02:02 UTCEG score recompute
  3. 2026-08-21 02:02 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:06 UTCGHSA enrichment
  6. 2026-08-20 18:11 UTCGHSA enrichment
  7. 2026-08-20 14:16 UTCGHSA enrichment
  8. 2026-08-20 10:13 UTCGHSA enrichment
  9. 2026-08-20 06:18 UTCGHSA enrichment
  10. 2026-08-20 02:23 UTCGHSA enrichment
  11. 2026-08-19 22:27 UTCGHSA enrichment
  12. 2026-08-19 18:32 UTCEG score recompute
  13. 2026-08-19 18:31 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:36 UTCGHSA enrichment
  16. 2026-08-19 10:40 UTCGHSA enrichment
  17. 2026-08-19 06:44 UTCGHSA enrichment
  18. 2026-08-19 02:45 UTCGHSA enrichment
  19. 2026-08-18 22:48 UTCGHSA enrichment
  20. 2026-08-18 18:53 UTCGHSA enrichment
  21. 2026-08-18 14:58 UTCGHSA enrichment
  22. 2026-08-18 10:44 UTCGHSA enrichment
  23. 2026-08-18 06:47 UTCGHSA enrichment
  24. 2026-08-18 02:50 UTCGHSA enrichment
  25. 2026-08-17 22:55 UTCGHSA enrichment
Show 21 more
  1. 2026-08-17 19:00 UTCGHSA enrichment
  2. 2026-08-17 14:10 UTCEG score recompute
  3. 2026-08-17 14:10 UTCGHSA enrichment
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 10:14 UTCEG score recompute
  6. 2026-08-17 10:14 UTCGHSA enrichment
  7. 2026-08-17 06:20 UTCEG score recompute
  8. 2026-08-17 06:20 UTCGHSA enrichment
  9. 2026-08-17 05:59 UTCEG score recompute▲ 9.00
  10. 2026-08-17 05:59 UTCGHSA enrichment
  11. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9 · severity → CRITICAL
  12. 2026-08-17 05:31 UTCEG score recompute
  13. 2026-08-17 05:31 UTCGHSA enrichment
  14. 2026-08-17 05:24 UTCMITRE cvelistV5
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 06:38 UTCGHSA enrichment
  19. 2026-08-15 06:23 UTCNVD update
  20. 2026-08-15 06:08 UTCEG score recompute
  21. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72279?
CVE-2026-72279 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR KVM currently maps the L1 VNCR into the host stage-1 by relying entirely on the permissions of the guest stage-1. At the same time, it is entirely possible that the backing…
When was CVE-2026-72279 disclosed?
CVE-2026-72279 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-72279 actively exploited?
CVE-2026-72279 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 91.2% of all scored CVEs.
What is the CVSS score of CVE-2026-72279?
CVE-2026-72279 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-72279?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72279, 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-72279

Explore →

Is Your Infrastructure Affected by CVE-2026-72279?

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

Start Free Scan →Browse All CVEs