Quick answers
- Is CVE-2026-0125 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0125 being exploited in the wild.
- How severe is CVE-2026-0125?
- Informational severity, with a CVSS score of 7.8, published 16 June 2026.
- Which products and versions are affected?
- Google Pixel Devices Security patch levels before 2026-06-05.
- Is there a fix for CVE-2026-0125?
- A patch was published on 2026-06-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0125 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-0125?
- 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 use-after-free (UAF) vulnerability exists in the Pixel Video Processing Unit (VPU) kernel driver, specifically within multiple functions of the 'vpu_ioctl.c' component. The flaw is rooted in a race condition during IOCTL (Input/Output Control) operations, where memory may be accessed after it has been freed. A local attacker with no special privileges can exploit this race condition to achieve arbitrary code execution in the context of the kernel, leading to local privilege escalation (EoP). The vulnerability does not require user interaction. Google addressed this issue in the June 2026 Pixel Update Bulletin with security patch level 2026-06-05.
Affected products
- Google Pixel Devices Security patch levels before 2026-06-05
Timeline
- 2026-06-16: disclosed
- 2026-06-16: advisory
- 2026-06-05: patched