Adjacent privilege escalation via modem buffer overwrite
Published Dec 11, 2025 · Updated Dec 11, 2025
Out-of-bounds write in Android on supported Pixel devices allows remote authenticated users to escalate privileges through adjacent access. ss_DecodeLcsAssistDataReqMsg in ss_LcsManagement.c applies an incorrect bounds check while decoding LCS assistance data, allowing a write past the destination buffer. Low privileges are required to reach the modem path, and successful exploitation can compromise device data and operation without user interaction.
Summary
What happened
Out-of-bounds write in Android on supported Pixel devices allows remote authenticated users to escalate privileges through adjacent access. ss_DecodeLcsAssistDataReqMsg in ss_LcsManagement.c applies an incorrect bounds check while decoding LCS assistance data, allowing a write past the destination buffer. Low privileges are required to reach the modem path, and successful exploitation can compromise device data and operation without user interaction.
The record
- CVE
- CVE-2025-36924
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-787, CWE-120, T1404
- Attack vector
- adjacent
- 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