# CVE-2026-58844: Android kernel out-of-bounds read/write in IOMMU

Source: https://junglewise.ai/threats/cve-2026-58844-in-multiple-locations-there-is-a-possible-out-of-bounds-read  
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-58844 · Severity: info · Published 2026-11-02

The Android kernel contains an out-of-bounds read/write vulnerability in multiple IOMMU (input/output memory management unit) operations due to incorrect bounds checking. A local attacker with no special privileges can exploit this to escalate their access level on an Android device without requiring 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-58844 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58844 being exploited in the wild.

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

**Which products and versions are affected?** Google Android kernel Kernel versions prior to fixes in April 2026.

**Is there a fix for CVE-2026-58844?** 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-58844 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-58844?** Check whether you run Google Android kernel at an affected version. 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

The vulnerability exists in the ARM SMMU-v3 KVM IOMMU driver and related page table operations, affecting bounds checking in multiple locations. A local attacker can trigger an out-of-bounds read or write by leveraging missing locks in smmu_iotlb_sync() or incorrect block alignment calculations in map_pages(). The attack requires local code execution but yields privilege escalation.

## Affected products

- Google Android kernel Kernel versions prior to fixes in April 2026

## Timeline

- 2026-11-02: disclosed

## References

- [https://android.googlesource.com/kernel/common/+/2f86c81dc9453ed385c4f0703d6bd664d0997567](https://android.googlesource.com/kernel/common/+/2f86c81dc9453ed385c4f0703d6bd664d0997567)
- [https://android.googlesource.com/kernel/common/+/329d7c6e7215f52bb5922b4bcaa6bf713fa4ccff](https://android.googlesource.com/kernel/common/+/329d7c6e7215f52bb5922b4bcaa6bf713fa4ccff)

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