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.
Affected versions
Linux kernel versions
6.2
and later are affected. Fixed in
6.6.145,
6.12.97,
6.18.39,
7.1.4,
7.2-rc1
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-64286?
CVE-2026-64286 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.2 onward and has been patched in 6.6.145, 6.12.97, 6.18.39 and others. CVE-2026-64286 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64286?
Yes. CVE-2026-64286 has been patched. Fixed versions include 6.6.145, 6.12.97, 6.18.39 and others. If you are running Linux kernel 6.2 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64286 actively exploited?
No. CVE-2026-64286 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.