CVE-2017-13216

Name: CVE-2017-13216
Creator: NVD / NIST
Published: 2018-01-12T23:29:01.89+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.95%

Last modified Jun 17, 2026

CVE-2017-13216 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.95% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

0.95%

56.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-787

Affected Software

Vendor	Product	Versions
Google	Android	All versions

References

http://www.securityfocus.com/bid/102390Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1040106Third Party Advisory, VDB Entry
https://source.android.com/security/bulletin/2018-01-01Vendor Advisory
https://www.exploit-db.com/exploits/43464/Third Party Advisory, VDB Entry
http://www.securityfocus.com/bid/102390Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1040106Third Party Advisory, VDB Entry
https://source.android.com/security/bulletin/2018-01-01Vendor Advisory
https://www.exploit-db.com/exploits/43464/Third Party Advisory, VDB Entry

Timeline

Published: Jan 12, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-13216?

How severe is CVE-2017-13216?

Severity scoring for CVE-2017-13216 is pending analysis. The EPSS model estimates a 0.95% probability of exploitation in the next 30 days.

How do I fix CVE-2017-13216?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-13216?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST