Local privilege escalation via unchecked fence count
Published Jun 13, 2024 · Updated Aug 20, 2024
Out-of-bounds write in the LWIS kernel component in Google Android allows local users to escalate privileges without user interaction. The lwis_initialize_transaction_fences function fails to bound transaction fence data before writing beyond its destination in lwis_fence.c. Exploitation requires local code execution on an affected Pixel-family device but no additional execution privileges, and successful exploitation grants elevated access.
Summary
What happened
Out-of-bounds write in the LWIS kernel component in Google Android allows local users to escalate privileges without user interaction. The lwis_initialize_transaction_fences function fails to bound transaction fence data before writing beyond its destination in lwis_fence.c. Exploitation requires local code execution on an affected Pixel-family device but no additional execution privileges, and successful exploitation grants elevated access.
The record
- CVE
- CVE-2024-32921
- Published
- Jun 13, 2024
- Updated
- Aug 20, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=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.
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