Local privilege escalation via uninitialized reclaim data
Published Dec 11, 2025 · Updated Dec 11, 2025
Memory corruption in the Android kernel allows local users to elevate privileges through Trusty’s trusty_ffa_mem_reclaim path. The function in shared-mem-smcall.c uses uninitialized data while reclaiming FFA shared memory, corrupting memory. A local low-privileged user can trigger the flaw without user interaction, gaining elevated privileges on affected Pixel devices.
Summary
What happened
Memory corruption in the Android kernel allows local users to elevate privileges through Trusty’s trusty_ffa_mem_reclaim path. The function in shared-mem-smcall.c uses uninitialized data while reclaiming FFA shared memory, corrupting memory. A local low-privileged user can trigger the flaw without user interaction, gaining elevated privileges on affected Pixel devices.
The record
- CVE
- CVE-2025-36935
- Published
- Dec 11, 2025
- Updated
- Dec 11, 2025
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-457, CWE-787, 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?
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