Skip to main content
← All vulnerabilities
CVE-2026-64286

KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.6.145, 6.12.97, 6.18.39, 7.1.4
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From be66e67f175096f283c9d5614c4991fc9e7ed975 · fixed in 477145860dba4c30f0b4e36f02f4c5291c1c888b; From be66e67f175096f283c9d5614c4991fc9e7ed975 · fixed in dfaef40d8a1533940fc1af788d70fce07362b4ce; From be66e67f175096f283c9d5614c4991fc9e7ed975 · fixed in 6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa; From be66e67f175096f283c9d5614c4991fc9e7ed975 · fixed in d4f4d61715d1061ba83b88196a3605662be30750; From be66e67f175096f283c9d5614c4991fc9e7ed975 · fixed in e8042f6e1d7befb2fb6b10a75918642bcd0acf9a

  • Linux Linux

    6.2

  • KernelLinux

    From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4

References 5

git.kernel.org