Local privilege escalation via improperly locked use-after-free
Published Aug 19, 2024 · Updated Aug 19, 2024
Use-after-free in the RIL component of Google Android allows local users to escalate privileges without user interaction. The sendDeviceState_1_6 function in RadioExt.cpp can access freed memory because device-state handling is not properly locked. A low-privileged local process is required, and successful exploitation gains higher privileges on an affected Pixel device.
Summary
What happened
Use-after-free in the RIL component of Google Android allows local users to escalate privileges without user interaction. The sendDeviceState_1_6 function in RadioExt.cpp can access freed memory because device-state handling is not properly locked. A low-privileged local process is required, and successful exploitation gains higher privileges on an affected Pixel device.
The record
- CVE
- CVE-2024-32927
- Published
- Aug 19, 2024
- Updated
- Aug 19, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-416, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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
- 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