CVE-2026-53277

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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
5%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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.

Patch Availability(14)

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~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)7.0.13-1

Weakness Classification(2)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 36× in last 7d / 150× 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 236 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 02:50 UTCEG score recompute
  3. 2026-08-25 02:50 UTCVendor advisory
  4. 2026-08-25 02:50 UTCGHSA enrichment
  5. 2026-08-24 14:00 UTCEG score recompute
  6. 2026-08-24 14:00 UTCVendor advisory
  7. 2026-08-24 14:00 UTCGHSA enrichment
  8. 2026-08-24 01:12 UTCVendor advisory
  9. 2026-08-24 01:12 UTCGHSA enrichment
  10. 2026-08-23 12:24 UTCEG score recompute
  11. 2026-08-23 12:24 UTCVendor advisory
  12. 2026-08-23 12:24 UTCGHSA enrichment
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 23:36 UTCVendor advisory
  15. 2026-08-22 23:36 UTCGHSA enrichment
  16. 2026-08-22 10:48 UTCEG score recompute
  17. 2026-08-22 10:48 UTCVendor advisory
  18. 2026-08-22 10:48 UTCGHSA enrichment
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 21:59 UTCVendor advisory
  21. 2026-08-21 21:59 UTCGHSA enrichment
  22. 2026-08-21 09:07 UTCEG score recompute
  23. 2026-08-21 09:07 UTCVendor advisory
  24. 2026-08-21 09:07 UTCGHSA enrichment
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 19:58 UTCVendor advisory
  2. 2026-08-20 19:58 UTCGHSA enrichment
  3. 2026-08-20 07:05 UTCEG score recompute
  4. 2026-08-20 07:05 UTCVendor advisory
  5. 2026-08-20 07:05 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 14:20 UTCVendor advisory
  8. 2026-08-19 14:20 UTCGHSA enrichment
  9. 2026-08-19 01:29 UTCEG score recompute
  10. 2026-08-19 01:29 UTCVendor advisory
  11. 2026-08-19 01:29 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 07:23 UTCVendor advisory
  15. 2026-08-17 07:23 UTCGHSA enrichment
  16. 2026-08-16 18:35 UTCEG score recompute
  17. 2026-08-16 18:35 UTCVendor advisory
  18. 2026-08-16 18:35 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 05:45 UTCEG score recompute
  21. 2026-08-16 05:45 UTCVendor advisory
  22. 2026-08-16 05:45 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 16:58 UTCVendor advisory
  25. 2026-08-15 16:58 UTCGHSA enrichment
  26. 2026-08-15 04:10 UTCEG score recompute
  27. 2026-08-15 04:10 UTCVendor advisory
  28. 2026-08-15 04:10 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 15:21 UTCVendor advisory
  31. 2026-08-14 15:21 UTCGHSA enrichment
  32. 2026-08-14 02:33 UTCEG score recompute
  33. 2026-08-14 02:33 UTCVendor advisory
  34. 2026-08-14 02:33 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 13:45 UTCVendor advisory
  37. 2026-08-13 13:45 UTCGHSA enrichment
  38. 2026-08-13 00:47 UTCEG score recompute
  39. 2026-08-13 00:47 UTCVendor advisory
  40. 2026-08-13 00:47 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-12 11:59 UTCVendor advisory
  43. 2026-08-12 11:59 UTCGHSA enrichment
  44. 2026-08-11 23:11 UTCEG score recompute
  45. 2026-08-11 23:11 UTCVendor advisory
  46. 2026-08-11 23:11 UTCGHSA enrichment
  47. 2026-08-11 10:23 UTCEG score recompute
  48. 2026-08-11 10:23 UTCVendor advisory
  49. 2026-08-11 10:23 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-10 21:35 UTCVendor advisory
  52. 2026-08-10 21:35 UTCGHSA enrichment
  53. 2026-08-10 08:46 UTCVendor advisory
  54. 2026-08-10 08:46 UTCGHSA enrichment
  55. 2026-08-09 19:59 UTCEG score recompute
  56. 2026-08-09 19:59 UTCVendor advisory
  57. 2026-08-09 19:59 UTCGHSA enrichment
  58. 2026-08-09 13:46 UTCEPSS rescore
  59. 2026-08-09 07:11 UTCVendor advisory
  60. 2026-08-09 07:11 UTCGHSA enrichment
  61. 2026-08-08 18:23 UTCEG score recompute
  62. 2026-08-08 18:23 UTCVendor advisory
  63. 2026-08-08 18:23 UTCGHSA enrichment
  64. 2026-08-08 16:37 UTCEPSS rescore
  65. 2026-08-08 05:34 UTCVendor advisory
  66. 2026-08-08 05:34 UTCGHSA enrichment
  67. 2026-08-07 16:46 UTCEG score recompute
  68. 2026-08-07 16:46 UTCVendor advisory
  69. 2026-08-07 16:46 UTCGHSA enrichment
  70. 2026-08-07 03:58 UTCVendor advisory
  71. 2026-08-07 03:58 UTCGHSA enrichment
  72. 2026-08-06 15:10 UTCEG score recompute
  73. 2026-08-06 15:10 UTCVendor advisory
  74. 2026-08-06 15:10 UTCGHSA enrichment
  75. 2026-08-06 13:47 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 August 5, 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53277?
CVE-2026-53277 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
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.