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