dbcve.org
AndroidOperating system · Google

CVE-2025-36931

HIGH · 7.8 CVSS v3.1 Published 2025-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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 confidence

A missing bounds check in the GetHostAddress function in gxp_buffer.h allows an out of bounds write, enabling local privilege escalation without requiring additional execution privileges or user interaction.

MitigationImplement proper bounds checking in the GetHostAddress function before any buffer write operations to prevent out of bounds memory access.

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
AndroidOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the gxp_buffer.h header file in the system
    Search for the file gxp_buffer.h in the Android system image or source code tree. Common paths may include system/, vendor/, or kernel directories. Use 'find / -name gxp_buffer.h 2>/dev/null' or similar file search commands.
    Affected if The file exists in the environment, indicating the vulnerable component is present
  2. Identify the GetHostAddress function in gxp_buffer.h
    Open gxp_buffer.h and locate the GetHostAddress function definition. Use grep or a text editor to find 'GetHostAddress' and examine its implementation.
    Affected if The GetHostAddress function is found and contains buffer write operations without bounds checking
  3. Verify bounds checking is missing before buffer writes
    Review the GetHostAddress function code to confirm there is no validation of buffer sizes or indices before any memcpy, memmove, or direct buffer assignments occur. Look for absence of size checks or boundary conditions.
    Affected if The function performs buffer writes without prior bounds validation, leaving the out-of-bounds write vulnerability present
  4. Confirm the component using this function is enabled in the build
    Determine if the library or driver that includes gxp_buffer.h is included in the Android build. Check build configuration files, kernel config, or system partition for the compiled component.
    Affected if The vulnerable component is built into the Android system image and active

If gxp_buffer.h with the GetHostAddress function exists in your Android environment and lacks bounds checking before buffer write operations, your system is affected by this privilege escalation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper bounds checking in the GetHostAddress function before any buffer write operations to prevent out of bounds memory access.

Recommended fix Moderate confidence
  1. Check the Android Security Bulletin for the month when CVE-2025-36931 was addressed (refer to source.android.com/security-bulletin)
  2. Apply the latest Android security update available for your device
  3. Verify the security patch level has been updated to include the fix for this CVE
  4. For devices no longer receiving official security updates, consider upgrading to a device that still receives monthly security patches
Caveat Devices that are no longer supported by the manufacturer may not receive this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36931 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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