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.

No CVSS v4.0

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00209.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
Linux Linux unaffected
Version Status Constraints
be66e67f175096f283c9d5614c4991fc9e7ed975 affected < 477145860dba4c30f0b4e36f02f4c5291c1c888b
be66e67f175096f283c9d5614c4991fc9e7ed975 affected < dfaef40d8a1533940fc1af788d70fce07362b4ce
be66e67f175096f283c9d5614c4991fc9e7ed975 affected < 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa
be66e67f175096f283c9d5614c4991fc9e7ed975 affected < d4f4d61715d1061ba83b88196a3605662be30750
be66e67f175096f283c9d5614c4991fc9e7ed975 affected < e8042f6e1d7befb2fb6b10a75918642bcd0acf9a
Linux Linux affected
Version Status Constraints
6.2 affected —
0 unaffected < 6.2
6.6.145 unaffected ≤ 6.6.*
6.12.97 unaffected ≤ 6.12.*
6.18.39 unaffected ≤ 6.18.*
7.1.4 unaffected ≤ 7.1.*
7.2-rc1 unaffected ≤ *

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

Vendors Products
Linux Subscribe
Linux Kernel Subscribe

Project Subscriptions

Vendors Products
Linux Subscribe
Linux Kernel Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://git.kernel.org/stable/c/477145860dba4c30f0b4e36f02f4c5291c1c888b cve-icon
https://git.kernel.org/stable/c/6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa cve-icon
https://git.kernel.org/stable/c/d4f4d61715d1061ba83b88196a3605662be30750 cve-icon
https://git.kernel.org/stable/c/dfaef40d8a1533940fc1af788d70fce07362b4ce cve-icon
https://git.kernel.org/stable/c/e8042f6e1d7befb2fb6b10a75918642bcd0acf9a cve-icon
History

Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-25T08:49:27.542Z

Reserved: 2026-07-19T15:36:31.778Z

Link: CVE-2026-64286

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-25T11:30:04Z

Weaknesses

No weakness.