Local privilege escalation via missing LCS enforcement
Published Sep 13, 2024 · Updated Sep 15, 2025
Privilege escalation in Google Android on Pixel devices before 2024-09-05 allows local users to gain elevated privileges. The Pixel LCS component retains test/debug code in production that omits LCS signing enforcement. Local code execution is required, but user interaction and additional execution privileges are not; successful exploitation grants higher device privileges.
Summary
What happened
Privilege escalation in Google Android on Pixel devices before 2024-09-05 allows local users to gain elevated privileges. The Pixel LCS component retains test/debug code in production that omits LCS signing enforcement. Local code execution is required, but user interaction and additional execution privileges are not; successful exploitation grants higher device privileges.
The record
- CVE
- CVE-2024-44092
- Published
- Sep 13, 2024
- Updated
- Sep 15, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-489, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=0 <*
- 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.
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