Physical privilege escalation via U-Boot fault injection
Published Dec 11, 2025 · Updated Dec 11, 2025
Elevation of privilege in Google Android's Pixel Tablet Dock U-Boot allows physically proximate attackers to gain elevated privileges. The append_uint32_le() routine contains a logic error that permits fault injection, but Google has not published the erroneous operation. Physical access to the dock is required; no prior execution privilege or user interaction is required, and the result is limited to elevation of privilege.
Summary
What happened
Elevation of privilege in Google Android's Pixel Tablet Dock U-Boot allows physically proximate attackers to gain elevated privileges. The append_uint32_le() routine contains a logic error that permits fault injection, but Google has not published the erroneous operation. Physical access to the dock is required; no prior execution privilege or user interaction is required, and the result is limited to elevation of privilege.
The record
- CVE
- CVE-2025-36938
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-693
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record 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.
Weakness, pattern, technique
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