CVE-2026-53277

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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: Take the SRCU lock for page table walks in fault injection and AT emulation

walk_s1() and kvm_walk_nested_s2() expect to be called while holding kvm->srcu to guard against memslot changes. While this is generally the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the respective walkers without taking kvm->srcu.

Fix by acquiring kvm->srcu prior to the table walk in both instances.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
1.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97706097f9b851cfe55c3b00b083dfc2bcf542bc

Vendor Advisories for CVE-2026-53277(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 54× 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-07-07 02:18 UTCEG score recompute
  2. 2026-07-07 02:18 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:14 UTCEG score recompute
  6. 2026-07-06 13:13 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:20 UTCEG score recompute
  10. 2026-07-06 00:19 UTCGHSA enrichment
  11. 2026-07-05 11:31 UTCEG score recompute
  12. 2026-07-05 11:30 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 22:40 UTCEG score recompute
  16. 2026-07-04 22:40 UTCGHSA enrichment
  17. 2026-07-04 09:52 UTCEG score recompute
  18. 2026-07-04 09:52 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 21:01 UTCEG score recompute
  22. 2026-07-03 21:00 UTCGHSA enrichment
  23. 2026-07-03 08:12 UTCEG score recompute
  24. 2026-07-03 08:12 UTCGHSA enrichment
  25. 2026-07-02 19:24 UTCEG score recompute
Show 29 more
  1. 2026-07-02 19:24 UTCGHSA enrichment
  2. 2026-07-02 06:36 UTCEG score recompute
  3. 2026-07-02 06:36 UTCGHSA enrichment
  4. 2026-07-01 17:47 UTCEG score recompute
  5. 2026-07-01 17:47 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 04:57 UTCEG score recompute
  8. 2026-07-01 04:56 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 16:08 UTCEG score recompute
  11. 2026-06-30 16:08 UTCGHSA enrichment
  12. 2026-06-30 03:20 UTCEG score recompute
  13. 2026-06-30 03:20 UTCGHSA enrichment
  14. 2026-06-29 14:32 UTCEG score recompute
  15. 2026-06-29 14:32 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 01:44 UTCEG score recompute
  19. 2026-06-29 01:44 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 12:55 UTCEG score recompute 8.80
  22. 2026-06-28 12:55 UTCGHSA enrichment
  23. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-25 10:03 UTCEG score recompute
  29. 2026-06-25 10:02 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53277?
CVE-2026-53277 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation walks1() and kvmwalknesteds2() expect to be called while holding kvm->srcu to guard against memslot changes. While this is generally the case,…
When was CVE-2026-53277 disclosed?
CVE-2026-53277 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53277 actively exploited?
CVE-2026-53277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53277?
CVE-2026-53277 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53277, 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-53277

Explore →

Is Your Infrastructure Affected by CVE-2026-53277?

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