Local privilege escalation via battery bounds-check omission
Published Jan 2, 2024 · Updated Jun 18, 2025
An out-of-bounds write in MediaTek's battery component on Android 12.0 and 13.0 allows local users with System privileges to escalate privileges. The component omits a bounds check and writes outside the intended memory buffer; MediaTek has not disclosed the affected function or input path. Exploitation requires existing System execution privileges and no user interaction; successful corruption enables privilege escalation.
Summary
What happened
An out-of-bounds write in MediaTek's battery component on Android 12.0 and 13.0 allows local users with System privileges to escalate privileges. The component omits a bounds check and writes outside the intended memory buffer; MediaTek has not disclosed the affected function or input path. Exploitation requires existing System execution privileges and no user interaction; successful corruption enables privilege escalation.
The record
- CVE
- CVE-2023-32882
- Published
- Jan 2, 2024
- Updated
- Jun 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jun 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- PhantomMap exploitability demonstrationproof of concept · demonstrated
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