# CVE-2026-59045: Android Kernel KVM race condition memory corruption

Source: https://junglewise.ai/threats/cve-2026-59045-in-multiple-locations-there-is-a-possible-memory-corruption-due  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-59045 · Severity: info · Published 2026-11-02

The Android kernel contains a race condition in KVM virtualization support on ARM64 processors that can cause memory corruption. A local attacker with basic user privileges can exploit this to gain higher-level access to the system without needing to interact with the user or obtain special permissions.

Technologies: [Google Android kernel](https://junglewise.ai/threats/technologies/google-android-kernel). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://android.googlesource.com/kernel/common/+/01ff2abe4905798e330a70f2970ee33a44419d24](https://android.googlesource.com/kernel/common/+/01ff2abe4905798e330a70f2970ee33a44419d24)
- [https://android.googlesource.com/kernel/common/+/22ae719f35b14f88e551f0e858a1087a4b721204](https://android.googlesource.com/kernel/common/+/22ae719f35b14f88e551f0e858a1087a4b721204)

## Related threats

- [Android kernel SMMU stale TLB entry escalation](https://junglewise.ai/threats/cve-2026-56930-in-smmu-find-ste-of-smmu-c-there-is-a-possible-way-to-retain)
- [Android Kernel out-of-bounds read in KVM trace buffer initialization](https://junglewise.ai/threats/cve-2026-59048-in-rb-cpu-init-of-trace-c-there-is-a-possible-out-of-bounds-read)
- [Android kernel out-of-bounds write in pKVM MMU race condition](https://junglewise.ai/threats/cve-2026-59042-in-pkvm-pages-to-ppages-of-mmu-c-there-is-a-possible-out-of)
- [Android kernel integer overflow in VMA padding](https://junglewise.ai/threats/cve-2026-58845-in-multiple-locations-there-is-a-possible-out-of-bounds-write-due)
- [Android kernel out-of-bounds read/write in IOMMU](https://junglewise.ai/threats/cve-2026-58844-in-multiple-locations-there-is-a-possible-out-of-bounds-read)