Quick answers
- Is CVE-2026-0178 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0178 being exploited in the wild.
- How severe is CVE-2026-0178?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel Devices Unspecified; fixed in security patch level 2026-11-05 or later.
- Is there a fix for CVE-2026-0178?
- Yes: fixed in Google 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-0178 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-0178?
- 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.
How to fix
- Fixed in: Google Pixel devices with security patch level 2026-11-05 or later
Technical details
A logic error in multiple functions of the arm-smmu-v3.c kernel driver fails to properly invalidate or manage stream table entries, allowing stale entries to persist. An attacker with System execution privileges can exploit this to bypass DMA memory isolation controls. The vulnerability requires no user interaction and results in local privilege escalation.
Affected products
- Google Pixel devices Unspecified; fixed in security patch level 2026-11-05 or later
Timeline
- 2026-11-10: disclosed: Published in Pixel Update Bulletin