SECUFOCUSNOW
Home›CVE index›CVE-2026-64287
Review reviewHigh

CVE-2026-64287

Linux

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<n>_EL2 (host -> EL2). Fix by clamping used_lrs to the...

CVSS
8.2
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 8.2

Vulnerability overview

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<n>_EL2 (host -> EL2). Fix by clamping used_lrs to the...

Affected product and versions

Product
Linux
Affected versions
>= be66e67f175096f283c9d5614c4991fc9e7ed975 < 2c5e72b9fbf83fdfa724e9f1af0f418ccf8739b8, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < 9fa301d8298778dd799fa4dcf7a7f440715d146e, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < c646431865f4b1a5b14067233fa27b11e05e0d46, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < 7fca3fcef81c713bc82a37bf741e0f28e6d04a6f, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < 8cc8bbbfab14c22c5551d0dd19b208a44b141c76, >= 6.2
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CWE
Not available