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

CVE-2026-64286

Linux

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vCPU context into the hyp's private vCPU on every run. ctxt_to_vcpu() expects a guest context to have a NULL __hyp_running_vcpu, which is only ever set on the host context, so that it resolves the vCPU via container_of(). While this is generally the case, flush_hyp_vcpu() copies the context verbatim and does not enforce this, so a value provided by the host is dereferenced at EL2 (host -> EL2). Fix by clearing __hyp_running...

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: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU flush_hyp_vcpu() copies the host vCPU context into the hyp's private vCPU on every run. ctxt_to_vcpu() expects a guest context to have a NULL __hyp_running_vcpu, which is only ever set on the host context, so that it resolves the vCPU via container_of(). While this is generally the case, flush_hyp_vcpu() copies the context verbatim and does not enforce this, so a value provided by the host is dereferenced at EL2 (host -> EL2). Fix by clearing __hyp_running...

Affected product and versions

Product
Linux
Affected versions
>= be66e67f175096f283c9d5614c4991fc9e7ed975 < 477145860dba4c30f0b4e36f02f4c5291c1c888b, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < dfaef40d8a1533940fc1af788d70fce07362b4ce, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < d4f4d61715d1061ba83b88196a3605662be30750, >= be66e67f175096f283c9d5614c4991fc9e7ed975 < e8042f6e1d7befb2fb6b10a75918642bcd0acf9a, >= 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