Quick answers
- Is CVE-2026-58801 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58801 being exploited in the wild.
- How severe is CVE-2026-58801?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Devices prior to 2026-11-05 security patch.
- Is there a fix for CVE-2026-58801?
- 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-58801 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58801?
- Check whether you run 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
A logic error in the smmu_domain_config_s1 function of arm-smmu-v3.c allows access to stale stream table entries when stream identifiers are reused across different protection domains. The vulnerability requires system execution privileges and no user interaction. An attacker can read residual data from previous stream configurations.
Affected products
- Google Pixel devices prior to 2026-11-05 security patch
Timeline
- 2026-11-10: disclosed
- 2026-11-10: advisory: Published in Pixel Update Bulletin—November 2026