CVE-2026-64286

Medium

Elevated severity or exploit probability.

CVSS base

8.2 HIGH

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS — probability of exploitation (30 days)

0.2%

7.3th percentile

CISA KEV

Not listed

Weakness / dates

—

Published 2026-07-25 · modified 2026-08-17

CVSS breakdown

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector	L	Local
Attack Complexity	L	Low
Privileges Required	H	High
User Interaction	N	None
Scope	C	Changed
Confidentiality	H	High
Integrity	H	High
Availability	H	High

Timeline

2026-07-25 — Published (NVD)
2026-08-17 — Last modified (NVD)

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.

Affected

linux

References

Official: NVD · CVE.org