CVE-2026-53277

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM 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 — 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

A fix is available — apply it.

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(medium)
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
1%
KEV
Not listed

Published

June 25, 2026

Last Modified

September 9, 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(2)

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

Patch Availability(16)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(2)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 11× in last 7d / 61× 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.

Showing the most recent 100 of 270 total refreshes for this CVE.

  1. 2026-09-18 07:28 UTCEG score recompute
  2. 2026-09-18 07:28 UTCVendor advisory
  3. 2026-09-18 07:28 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-14 01:22 UTCVendor advisory
  6. 2026-09-14 01:21 UTCGHSA enrichment
  7. 2026-09-13 09:40 UTCVendor advisory
  8. 2026-09-13 09:40 UTCGHSA enrichment
  9. 2026-09-12 15:51 UTCEG score recompute
  10. 2026-09-12 15:51 UTCVendor advisory
  11. 2026-09-12 15:51 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 13:39 UTCEG score recompute
  15. 2026-09-09 13:39 UTCVendor advisory
  16. 2026-09-09 13:39 UTCGHSA enrichment
  17. 2026-09-09 12:37 UTCEG score recompute
  18. 2026-09-09 12:37 UTCVendor advisory
  19. 2026-09-09 12:37 UTCGHSA enrichment
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-08-30 19:36 UTCEG score recompute
  25. 2026-08-30 19:36 UTCVendor advisory
Show 75 more
  1. 2026-08-30 19:36 UTCGHSA enrichment
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 23:56 UTCEG score recompute
  6. 2026-08-27 23:56 UTCVendor advisory
  7. 2026-08-27 23:56 UTCGHSA enrichment
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 02:50 UTCEG score recompute
  12. 2026-08-25 02:50 UTCVendor advisory
  13. 2026-08-25 02:50 UTCGHSA enrichment
  14. 2026-08-24 14:00 UTCEG score recompute
  15. 2026-08-24 14:00 UTCVendor advisory
  16. 2026-08-24 14:00 UTCGHSA enrichment
  17. 2026-08-24 01:12 UTCVendor advisory
  18. 2026-08-24 01:12 UTCGHSA enrichment
  19. 2026-08-23 12:24 UTCEG score recompute
  20. 2026-08-23 12:24 UTCVendor advisory
  21. 2026-08-23 12:24 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 23:36 UTCVendor advisory
  24. 2026-08-22 23:36 UTCGHSA enrichment
  25. 2026-08-22 10:48 UTCEG score recompute
  26. 2026-08-22 10:48 UTCVendor advisory
  27. 2026-08-22 10:48 UTCGHSA enrichment
  28. 2026-08-21 23:49 UTCEPSS rescore
  29. 2026-08-21 21:59 UTCVendor advisory
  30. 2026-08-21 21:59 UTCGHSA enrichment
  31. 2026-08-21 09:07 UTCEG score recompute
  32. 2026-08-21 09:07 UTCVendor advisory
  33. 2026-08-21 09:07 UTCGHSA enrichment
  34. 2026-08-20 22:55 UTCEPSS rescore
  35. 2026-08-20 19:58 UTCVendor advisory
  36. 2026-08-20 19:58 UTCGHSA enrichment
  37. 2026-08-20 07:05 UTCEG score recompute
  38. 2026-08-20 07:05 UTCVendor advisory
  39. 2026-08-20 07:05 UTCGHSA enrichment
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-19 14:20 UTCVendor advisory
  42. 2026-08-19 14:20 UTCGHSA enrichment
  43. 2026-08-19 01:29 UTCEG score recompute
  44. 2026-08-19 01:29 UTCVendor advisory
  45. 2026-08-19 01:29 UTCGHSA enrichment
  46. 2026-08-18 13:48 UTCEPSS rescore
  47. 2026-08-17 13:47 UTCEPSS rescore
  48. 2026-08-17 07:23 UTCVendor advisory
  49. 2026-08-17 07:23 UTCGHSA enrichment
  50. 2026-08-16 18:35 UTCEG score recompute
  51. 2026-08-16 18:35 UTCVendor advisory
  52. 2026-08-16 18:35 UTCGHSA enrichment
  53. 2026-08-16 14:56 UTCEPSS rescore
  54. 2026-08-16 05:45 UTCEG score recompute
  55. 2026-08-16 05:45 UTCVendor advisory
  56. 2026-08-16 05:45 UTCGHSA enrichment
  57. 2026-08-16 02:14 UTCEPSS rescore
  58. 2026-08-15 16:58 UTCVendor advisory
  59. 2026-08-15 16:58 UTCGHSA enrichment
  60. 2026-08-15 04:10 UTCEG score recompute
  61. 2026-08-15 04:10 UTCVendor advisory
  62. 2026-08-15 04:10 UTCGHSA enrichment
  63. 2026-08-15 01:30 UTCEPSS rescore
  64. 2026-08-14 15:21 UTCVendor advisory
  65. 2026-08-14 15:21 UTCGHSA enrichment
  66. 2026-08-14 02:33 UTCEG score recompute
  67. 2026-08-14 02:33 UTCVendor advisory
  68. 2026-08-14 02:33 UTCGHSA enrichment
  69. 2026-08-13 22:00 UTCEPSS rescore
  70. 2026-08-13 13:45 UTCVendor advisory
  71. 2026-08-13 13:45 UTCGHSA enrichment
  72. 2026-08-13 00:47 UTCEG score recompute
  73. 2026-08-13 00:47 UTCVendor advisory
  74. 2026-08-13 00:47 UTCGHSA enrichment
  75. 2026-08-12 13:51 UTCEPSS rescore

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 September 9, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.