Quick answers
- Is CVE-2026-58809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58809 being exploited in the wild.
- How severe is CVE-2026-58809?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Android Pixel devices with pKVM SMMU; ARM SMMU v3 as used in pKVM.
- Is there a fix for CVE-2026-58809?
- Yes: fixed in Android Pixel devices with security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58809 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58809?
- Check whether you run Android or ARM SMMU v3 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.
How to fix
- Fixed in: Android Pixel devices with security patch level 2026-11-05 or later
Technical details
The vulnerability is an out-of-bounds write in the smmu_domain_config_s1 function of arm-smmu-v3.c, caused by a missing bounds check on array or buffer operations. An attacker with System execution privileges can trigger this to write beyond buffer boundaries, affecting the pKVM SMMU (protected kernel virtual machine stage 2 SMMU). The vulnerability requires system-level access but no user interaction.
Affected products
- Android Pixel devices with pKVM SMMU
- ARM SMMU v3 as used in pKVM
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched: Security patch level 2026-11-05 or later addresses this issue for Pixel devices