Local privilege escalation via EdgeTPU use-after-free
Published Jun 16, 2026 · Updated Jun 16, 2026
Use-after-free in Android's EdgeTPU kernel driver allows local users with System privileges to elevate privileges without interaction. The edgetpu_sync_fence_group_shutdown() function continues to use freed memory while shutting down a synchronization-fence group. Exploitation requires local code already running with System privileges; Google reports no user interaction and only elevation of privilege as the consequence.
Summary
What happened
Use-after-free in Android's EdgeTPU kernel driver allows local users with System privileges to elevate privileges without interaction. The edgetpu_sync_fence_group_shutdown() function continues to use freed memory while shutting down a synchronization-fence group. Exploitation requires local code already running with System privileges; Google reports no user interaction and only elevation of privilege as the consequence.
The record
- CVE
- CVE-2026-0137
- Published
- Jun 16, 2026
- Updated
- Jun 16, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 16, 2026CVE publishedPublication date reported by the CVE source.
- Jun 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo