Local privilege escalation via allocator use-after-free
Published Oct 25, 2024 · Updated Oct 25, 2024
Use-after-free in the LWIS allocator on Google Pixel devices allows local users to escalate privileges through the Android kernel. The lwis_allocator_free function permits access to allocator memory after it has been freed, resulting in memory corruption. Exploitation requires local code execution but needs no additional execution privileges or user interaction; Google has not published further trigger details.
Summary
What happened
Use-after-free in the LWIS allocator on Google Pixel devices allows local users to escalate privileges through the Android kernel. The lwis_allocator_free function permits access to allocator memory after it has been freed, resulting in memory corruption. Exploitation requires local code execution but needs no additional execution privileges or user interaction; Google has not published further trigger details.
The record
- CVE
- CVE-2024-47033
- Published
- Oct 25, 2024
- Updated
- Oct 25, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-416, T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 25, 2024CVE publishedPublication date reported by the CVE source.
- Oct 25, 2024Record 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 <*
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