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

CVE-2026-0150

CVE-2026-0150

Description

Integer overflow in EdgeTPU firmware's ExecuteGraph command leads to out-of-bounds write and local privilege escalation on Pixel devices.

AI Insight

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

Integer overflow in EdgeTPU firmware's ExecuteGraph command leads to out-of-bounds write and local privilege escalation on Pixel devices.

Vulnerability

In the ExecuteGraph command handler of the EdgeTPU firmware, an integer overflow vulnerability exists that can lead to an out-of-bounds write. The affected firmware is present on supported Pixel devices. The specific versions affected are those prior to the security patch level 2026-06-05. The vulnerability requires local access and triggers when a crafted command is sent to the EdgeTPU firmware.

Exploitation

To exploit an attacker must have local access to the device. No user interaction is required. An integer overflow occurs in the ExecuteGraph command handler resulting in an out-of-bounds write to memory. An attacker can craft a specific command to trigger this overflow.

Impact

Successful exploitation can lead to local escalation of privilege potentially gaining root privileges. The out-of-bounds write could allow an attacker to overwrite critical data structures leading to arbitrary code execution in the context of the EdgeTPU firmware [1].

Mitigation

The issue is addressed in the June 2026 Pixel Update Bulletin [1]. Devices with a security patch level of 2026-06-05 or later are protected. Users should ensure their Pixel devices are updated to the latest available security patch.

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.