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.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-64286 is a high-severity vulnerability (CVSS 8.2) in the Linux kernel's KVM hypervisor implementation for ARM64 architecture. The flaw exists in the flush_hyp_vcpu() function, which fails to properly clear the __hyp_running_vcpu field when copying host vCPU context into the hypervisor's private vCPU. This creates a state management issue where the hypervisor expects guest contexts to have a NULL __hyp_running_vcpu value, but the function copies context verbatim without enforcing this invariant. The vulnerability affects systems running Linux kernels with KVM ARM64 support, particularly those using protected KVM (pKVM) for virtualization. While not yet in CISA's known exploited vulnerabilities list, the impact is significant for cloud providers, ARM-based server environments, and systems relying on KVM-based isolation.
Though currently unmapped to specific MITRE ATT&CK techniques, this vulnerability represents a privilege escalation and hypervisor escape risk pattern. Detection with Casky's extended reasoning would focus on identifying anomalous vCPU context state transitions, kernel memory corruption patterns during hypervisor-guest boundary crossings, and unusual resource access from guest VMs attempting to influence hypervisor execution paths. Practitioners using Casky would see findings related to kernel debugging artifacts showing improper context initialization, unexpected __hyp_running_vcpu persistence across vCPU flushes, and potential lateral movement attempts from guest to host contexts. The skill mapping would emphasize defensive monitoring for hypervisor state inconsistencies and ARM64-specific kernel integrity checks that distinguish legitimate vCPU operations from exploitation attempts.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-64286. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation