CVE-2026-64286

HIGHCVSS 8.2/10EPSS 0.17%

Last modified

CVE-2026-64286 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. 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(). EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

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_vcpu after the copy.

Metrics

CVSS 3.1
8.2/10

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS Probability
0.17%

6.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= be66e67f175096f283c9d5614c4991fc9e7ed975, < 477145860dba4c30f0b4e36f02f4c5291c1c888b; >= be66e67f175096f283c9d5614c4991fc9e7ed975, < dfaef40d8a1533940fc1af788d70fce07362b4ce; >= be66e67f175096f283c9d5614c4991fc9e7ed975, < 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa; >= be66e67f175096f283c9d5614c4991fc9e7ed975, < d4f4d61715d1061ba83b88196a3605662be30750; >= be66e67f175096f283c9d5614c4991fc9e7ed975, < e8042f6e1d7befb2fb6b10a75918642bcd0acf9a
LinuxLinux6.2

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64286?
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_vcpu after the copy.
How severe is CVE-2026-64286?
CVE-2026-64286 has a CVSS score of 8.2/10 (HIGH severity). The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64286?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64286?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST