Quick answers
- Is CVE-2026-58684 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58684 being exploited in the wild.
- How severe is CVE-2026-58684?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Firmware Before 2026-11-05 patch level.
- Is there a fix for CVE-2026-58684?
- Yes: fixed in 2026-11-05 security patch level or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58684 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-58684?
- Check whether you run Google Pixel Firmware 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: 2026-11-05 security patch level or later
Technical details
A logic error in the smmu_config_l3tt function of smmu.c in the ACFW firmware allows a local attacker to bypass permission checks. The vulnerability is classified as an escalation of privilege (EoP) requiring no additional execution privileges for exploitation. The advisory indicates no user interaction is needed to trigger the flaw.
Affected products
- Google Pixel firmware Before 2026-11-05 patch level
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched