Bug 2507123 (CVE-2026-64286) - CVE-2026-64286 kernel: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU
Summary: CVE-2026-64286 kernel: KVM: arm64: Clear __hyp_running_vcpu when flushing the...
Keywords:
Status: NEW
Alias: CVE-2026-64286
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-25 10:06 UTC by OSIDB Bzimport
Modified: 2026-07-30 03:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-25 10:06:15 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.