Local information disclosure via unchecked bounds
Published Apr 5, 2024 · Updated Mar 25, 2025
Out-of-bounds read in the Android kernel ACPM component allows local users to disclose information without user interaction. The tmu_get_gov_time_windows function reads beyond an intended buffer because it performs no bounds check before accessing time-window data. Local low-privileged access is required; the published consequence is limited to information disclosure, and the exposed memory contents are undisclosed.
Summary
What happened
Out-of-bounds read in the Android kernel ACPM component allows local users to disclose information without user interaction. The tmu_get_gov_time_windows function reads beyond an intended buffer because it performs no bounds check before accessing time-window data. Local low-privileged access is required; the published consequence is limited to information disclosure, and the exposed memory contents are undisclosed.
The record
- CVE
- CVE-2024-29744
- Published
- Apr 5, 2024
- Updated
- Mar 25, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 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.
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