VYPR
Unrated severityNVD Advisory· Published Jun 16, 2026· Updated Jun 16, 2026

CVE-2026-0125

CVE-2026-0125

Description

A use-after-free race condition in the Pixel Video Processing Unit driver allows local escalation of privilege without user interaction.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A use-after-free race condition in the Pixel Video Processing Unit driver allows local escalation of privilege without user interaction.

Vulnerability

In the vpu_ioctl.c file of the Pixel Video Processing Unit (VPU) kernel driver, multiple functions contain a use-after-free vulnerability due to a race condition [1]. This occurs when concurrent operations on shared memory objects are not properly synchronized, allowing a freed object to be accessed. The issue affects Pixel devices running a security patch level before 2026-06-05.

Exploitation

An attacker with local access to the device can trigger the race condition without requiring any additional execution privileges or user interaction [1]. The attacker must carefully time operations to exploit the window between freeing and reusing a memory object, but no special permissions are needed beyond normal user-level access.

Impact

Successful exploitation leads to local escalation of privilege (EoP) [1]. The attacker can gain elevated privileges within the kernel context, potentially allowing full control over the affected device's video processing capabilities and further system compromise.

Mitigation

Google addressed this vulnerability in the June 2026 Pixel Update Bulletin, with a fix included in the 2026-06-05 security patch level [1]. Users should ensure their Pixel devices are updated to this patch level or later. No workarounds are available; the only mitigation is applying the security update.

AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.