Local information disclosure via uninitialized TPU state
Published Jun 13, 2024 · Updated Nov 6, 2024
Information disclosure in the Android kernel allows local users to read uninitialized data through the TPU state interface. The tpu_get_int_state function in tpu.c processes TPU state with uninitialized data, allowing unintended information to be returned by the ACPM component. Low-privileged local access is required, no user interaction is needed, and the reported consequence is limited to information disclosure.
Summary
What happened
Information disclosure in the Android kernel allows local users to read uninitialized data through the TPU state interface. The tpu_get_int_state function in tpu.c processes TPU state with uninitialized data, allowing unintended information to be returned by the ACPM component. Low-privileged local access is required, no user interaction is needed, and the reported consequence is limited to information disclosure.
The record
- CVE
- CVE-2024-32914
- Published
- Jun 13, 2024
- Updated
- Nov 6, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 6, 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.
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