Local privilege escalation via incorrect bounds check
Published Dec 11, 2025 · Updated Dec 11, 2025
Out-of-bounds write in the TPU GetHostAddress path in Google Android kernel allows local users to escalate privileges without interaction. GetHostAddress in gxp_buffer.h applies an incorrect bounds check before writing a host address, allowing the destination buffer boundary to be crossed. A low-privileged local foothold is required, and successful exploitation grants elevated Android privileges without user interaction.
Summary
What happened
Out-of-bounds write in the TPU GetHostAddress path in Google Android kernel allows local users to escalate privileges without interaction. GetHostAddress in gxp_buffer.h applies an incorrect bounds check before writing a host address, allowing the destination buffer boundary to be crossed. A low-privileged local foothold is required, and successful exploitation grants elevated Android privileges without user interaction.
The record
- CVE
- CVE-2025-36928
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-787, CWE-120, T1404
- Attack vector
- local
- Privileges
- authenticated
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