# CVE-2026-59598: Google Pixel EdgeTPU Driver use-after-free in rio watchdog handler

Source: https://junglewise.ai/threats/cve-2026-59598-in-platform-rio-ncp-wdt-handler-of-edgetpu-rio-c-there-is-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-59598 · Severity: info · Published 2026-11-10

Google Pixel devices include an EdgeTPU driver component that is vulnerable to a use-after-free memory error in the RIO watchdog timer handler. An attacker with local access to a Pixel device could exploit this flaw to escalate privileges and execute arbitrary code with elevated permissions. This could allow complete compromise of the device if exploited.

Technologies: [Google Pixel](https://junglewise.ai/threats/technologies/google-pixel). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-59598 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59598 being exploited in the wild.

**How severe is CVE-2026-59598?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel prior to 2026-11-05 patch level.

**Is there a fix for CVE-2026-59598?** Yes: fixed in Pixel devices with 2026-11-05 security patch level or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-59598 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-59598?** Check whether you run Google Pixel 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 Pixel devices with 2026-11-05 security patch level or later

## Technical details

A use-after-free vulnerability exists in the platform_rio_ncp_wdt_handler function of edgetpu_rio.c in the EdgeTPU Driver. The vulnerability requires local access and user interaction to exploit, allowing an attacker to escalate privileges to execute arbitrary code on the device. The fixed patch level is 2026-11-05.

## Affected products

- Google Pixel prior to 2026-11-05 patch level

## Timeline

- 2026-11-10: disclosed
- 2026-11-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google Pixel coprocessor memory privilege escalation](https://junglewise.ai/threats/cve-2026-95404-in-multiple-locations-there-is-a-possible-way-to-modify)
- [Google Pixel shared memory bitmap out-of-bounds write](https://junglewise.ai/threats/cve-2026-95403-in-multiple-locations-there-is-a-possible-way-to-trigger-an-out)
- [Google Pixel HWCodec buffer overflow in HEVC decoder](https://junglewise.ai/threats/cve-2026-95402-in-slice-header-of-hevc-decoder-there-is-a-possible-non-heap)
- [Google Pixel hevc_decoder buffer overflow](https://junglewise.ai/threats/cve-2026-95401-in-knee-function-info-of-hevc-decoder-there-is-a-possible-non)
- [Google Pixel FaceAuth race condition in biometric enrollment](https://junglewise.ai/threats/cve-2026-95399-in-multiple-functions-of-face-status-h-there-is-a-possible-way-to)