---
id: CVE-2026-64286
title: |-
  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
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_vc…
severity: high
cvss: 8.2
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H'
published: '2026-07-25'
updated: '2026-07-27'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-64286'
references:
  - url: 'https://git.kernel.org/stable/c/477145860dba4c30f0b4e36f02f4c5291c1c888b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6bea2f8becdb20d34378493c3b77a9b9cf8c6cfa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d4f4d61715d1061ba83b88196a3605662be30750'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/dfaef40d8a1533940fc1af788d70fce07362b4ce'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e8042f6e1d7befb2fb6b10a75918642bcd0acf9a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00175
epssPercentile: 0.0728
ingestedAt: '2026-07-27T06:16:50.092Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.