Cyber Resilience

CVE-2025-20695

Memory Safety in Google Android 13.0 … 15.0

Memory Safety
Published
08 July 2025
Modified
17 June 2026
Patch / advisory
View 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-20695 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 SA-15 (Development Process, Standards, and Tools) — 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: ALPS09741871; Issue ID:…

more

MSV-3317.

CWE(s)
CWE-124CWE-787

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.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-20694Same product: Google Android
CVE-2024-20103Same product: Google Android
CVE-2024-20029Same product: Google Android
CVE-2024-20101Same product: Google Android
CVE-2023-20775Same product: Google Android
CVE-2024-20100Same product: Google Android
CVE-2024-20146Same product: Google Android
CVE-2024-20072Same product: Mediatek Mt6990
CVE-2025-20658Same product: Google Android
CVE-2025-20656Same 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

SA-11 Developer Testing and Evaluation good match

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

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SI-10 Information Input Validation partial match

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

SI-16 Memory Protection partial match

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.

A.8.29 Security testing in development and acceptance mostly match
finds

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

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

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

A.8.27 Secure system architecture and engineering principles partial match
prevents

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

A.8.28 Secure coding partial match
prevents

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

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References