Local stack-data disclosure via uninitialized buffer
Published Jun 13, 2024 · Updated Mar 18, 2025
Information disclosure in Google Android's hwbcc TA allows local users to read uninitialized stack data during privilege removal. hwbcc_ns_deprivilege in trusty/user/base/lib/hwbcc/client/hwbcc.c exposes stack contents because data used by the deprivileging path is not initialized before disclosure. Low execution privileges are required, no user interaction is needed, and the documented consequence is limited to local confidentiality loss.
Summary
What happened
Information disclosure in Google Android's hwbcc TA allows local users to read uninitialized stack data during privilege removal. hwbcc_ns_deprivilege in trusty/user/base/lib/hwbcc/client/hwbcc.c exposes stack contents because data used by the deprivileging path is not initialized before disclosure. Low execution privileges are required, no user interaction is needed, and the documented consequence is limited to local confidentiality loss.
The record
- CVE
- CVE-2024-29780
- Published
- Jun 13, 2024
- Updated
- Mar 18, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-908, T1005
- 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.
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