Quick answers
- Is CVE-2026-56966 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56966 being exploited in the wild.
- How severe is CVE-2026-56966?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Pixel firmware.
- Is there a fix for CVE-2026-56966?
- Yes: fixed in Google Pixel 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-56966 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-56966?
- Check whether you run Google Pixel Firmware. 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 security patch level 2026-11-05 or later
Technical details
The vulnerability exists in the CommitToBuffer function of hal_override_options.bundle.cc, where improper memory mapping cleanup allows stale direct memory access (DMA) mappings to secure memory to persist due to a confused deputy condition. A local attacker with system execution privileges can exploit this to access secure memory regions that should be inaccessible. The Google Pixel November 2026 security update (patch level 2026-11-05 or later) addresses this issue.
Affected products
- Google Pixel firmware
Timeline
- 2026-11-10: disclosed