Local information disclosure via unchecked gov_init bounds
Published Apr 5, 2024 · Updated Mar 28, 2025
An out-of-bounds read in the Android kernel allows local users to disclose memory through gov_init without user interaction. The gov_init routine omits a bounds check before reading, causing access beyond the intended memory boundary. Exploitation requires local low-privileged access and is limited to information disclosure; Google identifies ACPM as the affected Pixel subcomponent.
Summary
What happened
An out-of-bounds read in the Android kernel allows local users to disclose memory through gov_init without user interaction. The gov_init routine omits a bounds check before reading, causing access beyond the intended memory boundary. Exploitation requires local low-privileged access and is limited to information disclosure; Google identifies ACPM as the affected Pixel subcomponent.
The record
- CVE
- CVE-2024-29738
- Published
- Apr 5, 2024
- Updated
- Mar 28, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-125, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 28, 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?
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