Local information disclosure via out-of-bounds read
Published Feb 11, 2022 · Updated Aug 4, 2024
Out-of-bounds read in the Android kernel's google_battery component allows local users to disclose information without user interaction. The Pixel bulletin identifies google_battery as the affected component, but Google marks the underlying Android bug nonpublic and does not disclose the buffer operation or triggering input. Exploitation requires a local low-privileged context on an affected Pixel device and exposes memory contents without reported integrity or availability impact.
Summary
What happened
Out-of-bounds read in the Android kernel's google_battery component allows local users to disclose information without user interaction. The Pixel bulletin identifies google_battery as the affected component, but Google marks the underlying Android bug nonpublic and does not disclose the buffer operation or triggering input. Exploitation requires a local low-privileged context on an affected Pixel device and exposes memory contents without reported integrity or availability impact.
The record
- CVE
- CVE-2021-39688
- Published
- Feb 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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