Quick answers
- Is CVE-2026-58766 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58766 being exploited in the wild.
- How severe is CVE-2026-58766?
- High severity, with a CVSS score of 7.8, published 15 September 2026.
- Which products and versions are affected?
- Arm SMMU-v3 <UNKNOWN>; Google Pixel Devices All supported Pixel devices prior to 2026-09-05 patch level.
- Is there a fix for CVE-2026-58766?
- A patch was published on 2026-09-05: Security patch level 2026-09-05 or later addresses this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58766 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-58766?
- Check whether you run Arm SMMU-v3, Google Android or Google Pixel Devices 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 is a privilege escalation (EoP) in multiple functions of arm-smmu-v3.c caused by a logic error in the kernel code. It affects the ARM SMMU-v3 driver, which manages IOMMU and memory translation on ARM-based systems. The attack is local and requires no additional execution privileges; user interaction is not needed for exploitation. An attacker with local code execution could exploit this logic error to escalate privileges to kernel level. Patches addressing this issue were released in the September 2026 security bulletin affecting Pixel devices (patch level 2026-09-05 or later).
Affected products
- ARM SMMU-v3 <UNKNOWN>
- Google Pixel devices All supported Pixel devices prior to 2026-09-05 patch level
Timeline
- 2026-09-15: disclosed: Published in Pixel Update Bulletin
- 2026-09-05: patched: Security patch level 2026-09-05 or later addresses this issue