CVE-2026-64287

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.2EG
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.2Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU

flush_hyp_vcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it to stay within the number of implemented list registers. While this is generally the case, flush_hyp_vcpu() copies vgic_v3 verbatim and does not enforce this, so a value provided by the host is used at EL2 to index vgic_lr[] and access ICH_LR_EL2 (host -> EL2).

Fix by clamping used_lrs to the number of implemented list registers after the copy, as the trusted path already does in vgic_flush_lr_state(). The number of implemented list registers is constant after init, so it is replicated once from kvm_vgic_global_state.nr_lr into hyp_gicv3_nr_lr rather than read on every entry.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fa301d8298778dd799fa4dcf7a7f440715d146e
generic

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cc8bbbfab14c22c5551d0dd19b208a44b141c76
generic

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fca3fcef81c713bc82a37bf741e0f28e6d04a6f
generic

KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c5e72b9fbf83fdfa724e9f1af0f418ccf8739b8

Vendor Advisories for CVE-2026-64287(4)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
redhatkernel-0:6.12.0-211.52.1.el10_22026-09-08redhat
redhatkernel-0:5.14.0-687.45.1.el9_82026-09-08redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1—

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 28× in last 7d / 119× 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 239 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64287?
CVE-2026-64287 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU flushhypvcpu() copies the host vGIC state into the hyp's private vCPU on every run. The vGIC list register save and restore use used_lrs as their loop bound and expect it…
When was CVE-2026-64287 disclosed?
CVE-2026-64287 was first published in the National Vulnerability Database on July 25, 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-64287 actively exploited?
CVE-2026-64287 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 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64287?
CVE-2026-64287 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-64287?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64287, 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-64287

Explore →

Is Your Infrastructure Affected by CVE-2026-64287?

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

Start Free Scan →Browse All CVEs