Local data disclosure via uninitialized ACPM state
Published Jun 13, 2024 · Updated Mar 18, 2025
Use of uninitialized data in Google's Android ACPM kernel component allows local users to disclose information via aur_get_state. The aur_get_state path in aurora.c exposes state data that is not initialized before it is returned to the caller. Exploitation requires low-privileged local execution on an affected Google Pixel device, needs no user interaction, and affects confidentiality only.
Summary
What happened
Use of uninitialized data in Google's Android ACPM kernel component allows local users to disclose information via aur_get_state. The aur_get_state path in aurora.c exposes state data that is not initialized before it is returned to the caller. Exploitation requires low-privileged local execution on an affected Google Pixel device, needs no user interaction, and affects confidentiality only.
The record
- CVE
- CVE-2024-29785
- Published
- Jun 13, 2024
- Updated
- Mar 18, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 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