Cyber Resilience

CVE-2025-20694

Memory Safety in Google Android 13.0 … 15.0

Published
08 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0015 5th percentile
Risk Priority 48 floored blend · peak EPSS

Summary

CVE-2025-20694 is a medium-severity Buffer Underflow (CWE-124) vulnerability in Google Android. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Bluetooth FW, there is a possible system crash due to an uncaught exception. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09752821; Issue ID:…

more

MSV-3342.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-20695Same product: Google Android
CVE-2025-20693Same product: Google Android
CVE-2023-20775Same product: Google Android
CVE-2026-20411Same product: Google Android
CVE-2024-20101Same product: Google Android
CVE-2024-20103Same product: Google Android
CVE-2024-20100Same product: Google Android
CVE-2024-20138Same product: Google Android
CVE-2025-20780Same product: Google Android
CVE-2025-20798Same product: Google Android

Affected Assets

mediatek
software development kit
≤ 3.7
google
android
13.0, 14.0, 15.0
openwrt
openwrt
21.02.0, 23.05

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and analysis can discover buffer underwrite flaws before deployment but does not stop their introduction.

Input validation can enforce bounds on indices or pointers before buffer writes, structurally stopping underwrite conditions.

Memory protection mechanisms limit the blast radius of an out-of-bounds write even if the coding flaw exists.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent introduction of buffer underwrite flaws via coding standards, reviews, and testing.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover buffer underwrite issues but do not prevent their creation.

PR.PS-02 partial match
prevents

Patching removes instances of the weakness after discovery but does not address root-cause prevention in code.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches buffer-underflow defects before release.

prevents

Secure SDLC mandates input validation and bounds checking that directly prevent buffer underflow.

prevents

Application security requirements can specify buffer-size and pointer-safety rules.

prevents

Secure architecture and engineering principles require safe memory-handling patterns.

prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds checks.

References