# CVE-2017-13216: Memory corruption in Android

> A local attacker can exploit an out-of-bounds write in the Android kernel to execute arbitrary code with elevated privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-13216, GHSA-c895-rp2x-rjpv, UBUNTU-CVE-2017-13216

## What is CVE-2017-13216?

CVE-2017-13216 is a high-severity memory corruption vulnerability in Google Android, published on 12 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In ashmem_ioctl of ashmem.c, there is an out-of-bounds write due to insufficient locking when accessing asma. This could lead to a local elevation of privilege enabling code execution as a privileged process with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-66954097.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-13216?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2017-13216?

Apply the vendor's patch.

## Is CVE-2017-13216 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-13216 exists.

Public exploit code:

- Android - Inter-Process munmap due to Race Condition in ashmem (exploitdb)

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13216 and fix it if it is affected.

What it is: CVE-2017-13216 is a high-severity memory corruption vulnerability in Google Android, published on 12 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-13216 exists.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-13216/ (Markdown: https://insights.sbomify.com/CVE-2017-13216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-13216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-13216
- OSV: https://osv.dev/vulnerability/CVE-2017-13216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-13216/
Summaries are generated and may contain mistakes; the official description above is the record.