VDB

CVE-2017-13216

CVE-2017-13216 PUBLISHED

Reported by google_android · Published January 12, 2018

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.

Affected products

VendorProductVersions
Google Inc.AndroidAndroid kernel
Google Inc.Android*

Timeline

  • Jan 3, 2018 CVE Published
  • Jan 8, 2018 PoC Published (2 in total, the first dated here)
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Oct 24, 2025 CVE Updated
  • Apr 6, 2026 Security Advisory
  • Oct 3, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-13216
vulnetix vdb fixes CVE-2017-13216

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-13216/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • 102390 vdb-entryx_refsource_BID
  • x_refsource_CONFIRM
  • 43464 exploitx_refsource_EXPLOIT-DB
  • 1040106 vdb-entryx_refsource_SECTRACK
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›