CVE-2025-20797
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn battery, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10315812; Issue ID: MSV-5534.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an out-of-bounds write vulnerability in the battery subsystem caused by missing bounds checks. An attacker who already has System privilege can exploit this to escalate to higher privileges (likely root) without user interaction. The flaw allows writing data beyond allocated memory boundaries in the battery component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.0= 15.0= 16.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The version is 14.0, 15.0, or 16.0 specifically (exact match)
-
Verify battery subsystem patch levelCheck the battery/firmware update status in Settings > About Phone > Build number, or query the battery management subsystem via 'dumpsys battery' for patch metadataAffected if The battery component firmware has not received patch ALPS10315812 (patch level is earlier than the fix)
-
Confirm exploit requires System privilegeReview access logs and running processes to determine if any untrusted process or component currently holds System-level permissions on the deviceAffected if The device has been compromised with System-level access, meaning the privilege escalation path is relevant
A device is affected if it runs Android 14.0, 15.0, or 16.0 and the battery subsystem firmware has not been updated with patch ALPS10315812, particularly if System-level compromise is suspected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patch ALPS10315812 to update the battery component firmware. Since this requires System-level access, ensure proper access controls and monitor for signs of compromise on devices where the patch cannot be immediately applied.
- Check the Android system security patch level on the device to confirm if it includes the fix for ALPS10315812. Go to Settings > About Phone > Security Patch Level.
- If the device has not received a security update including Patch ID ALPS10315812, contact the device manufacturer (OEM) to request the patch or check if an update is available.
- Apply the vendor-supplied patch through the device's system update mechanism once released by the OEM.
- Verify after patching that the Security Patch Level reflects a date equal to or after the month the fix was released (typically included in subsequent Android security bulletins).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data