Quick answers
- Is CVE-2026-59045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59045 being exploited in the wild.
- How severe is CVE-2026-59045?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android Kernel.
- Is there a fix for CVE-2026-59045?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59045 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-59045?
- Check whether you run Google Android kernel. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A race condition exists in the pKVM (protected KVM) vCPU initialization code in arch/arm64/kvm/hyp/nvhe/pkvm.c, where concurrent attempts to initialize multiple protected virtual CPUs can cause unsynchronized access to shared state (pvmfw_entry_vcpu/primary_vcpu). An attacker with local execution can race multiple vCPU initialization calls to trigger memory corruption or state confusion, leading to privilege escalation within the hypervisor or host kernel.
Affected products
- Google Android Kernel