# CVE-2026-58824: Android kernel pKVM out-of-bounds write in trace buffer initialization

Source: https://junglewise.ai/threats/cve-2026-58824-in-pkvm-load-tracing-of-trace-c-there-is-a-possible-out-of-bounds  
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-58824 · Severity: info · Published 2026-11-02

A flaw in Android's protected kernel virtual machine (pKVM) tracing code allows local attackers to write beyond the bounds of a trace buffer due to an incorrect address validation. An attacker with local access could exploit this to gain privilege escalation without needing additional system permissions or user interaction.

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-58824 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58824 being exploited in the wild.

**How severe is CVE-2026-58824?** Informational severity, published 2 November 2026.

**Which products and versions are affected?** Google Android kernel.

**Is there a fix for CVE-2026-58824?** Yes: fixed in Android kernel commit 5a6735b89ba7c8684d36e2ecd9b02e834e97de9c and 8be8949794c96f10348fdd3d8dc7740fdfecd4e2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58824 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-58824?** 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.

## How to fix

- Fixed in Android kernel commit 5a6735b89ba7c8684d36e2ecd9b02e834e97de9c and 8be8949794c96f10348fdd3d8dc7740fdfecd4e2

## Technical details

The vulnerability exists in __pkvm_load_tracing() in arch/arm64/kvm/hyp/nvhe/trace.c, where rb_cpu_fits_desc() is invoked with an untrusted host virtual address rather than the correct hypervisor virtual address for trace descriptors. This causes subsequent bounds comparisons to be incorrect, leading to an out-of-bounds write. The fix involves passing the hypervisor VA instead of the host VA to perform correct bounds checking.

## Affected products

- Google Android kernel

## Timeline

- 2026-11-02: disclosed

## References

- [https://android.googlesource.com/kernel/common/+/5a6735b89ba7c8684d36e2ecd9b02e834e97de9c](https://android.googlesource.com/kernel/common/+/5a6735b89ba7c8684d36e2ecd9b02e834e97de9c)
- [https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2](https://android.googlesource.com/kernel/common/+/8be8949794c96f10348fdd3d8dc7740fdfecd4e2)

## 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 KVM race condition memory corruption](https://junglewise.ai/threats/cve-2026-59045-in-multiple-locations-there-is-a-possible-memory-corruption-due)
- [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)