Local information disclosure via optimized-away zeroing
Published Oct 25, 2021 · Updated Aug 3, 2024
Android kernel information disclosure before the relevant compiler fix allows local users to read residual memory through memzero_explicit. The compiler-clang.h implementation omitted barrier_data(), allowing Clang to optimize a zeroing call away and leave sensitive data uninitialized. Exploitation requires local code execution with low privileges and no user interaction; impact is confined to confidentiality.
Summary
What happened
Android kernel information disclosure before the relevant compiler fix allows local users to read residual memory through memzero_explicit. The compiler-clang.h implementation omitted barrier_data(), allowing Clang to optimize a zeroing call away and leave sensitive data uninitialized. Exploitation requires local code execution with low privileges and no user interaction; impact is confined to confidentiality.
The record
- CVE
- CVE-2021-0938
- Published
- Oct 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-908, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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