CVE-2016-6735
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn elevation of privilege vulnerability in the NVIDIA GPU driver in Android before 2016-11-05 could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device. Android ID: A-30907701. References: NVIDIA N-CVE-2016-6735.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA local elevation of privilege vulnerability in the NVIDIA GPU driver for Android allows a malicious application to execute arbitrary code within kernel context, achieving full device compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Android version is in affected rangeCheck the device settings or run 'getprop ro.build.version.release' to determine the installed Android OS versionAffected if The reported version is 7.0 (Nougat) or any earlier version such as 6.0, 5.1, 5.0, etc.
-
Identify NVIDIA GPU hardware presenceReview device specifications or use system information tools (such as 'lspci' on devices with accessible shells, or check /proc/cpuinfo for NVIDIA GPU identifiers) to determine if the device contains an NVIDIA GPUAffected if The device contains an NVIDIA GPU processor (such as Tegra series) and the Android version is 7.0 or below
-
Verify NVIDIA GPU driver is installedCheck for the presence of NVIDIA graphics driver files in the system partition or examine loaded kernel modules (using 'lsmod' or checking /proc/modules) for NVIDIA-related driversAffected if NVIDIA GPU driver modules are loaded and the Android version falls within the affected range
-
Assess kernel privilege escalation exposureConfirm the device kernel is unpatched by reviewing the security patch level in Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch'Affected if The security patch level is earlier than the November 2016 Android security update that addresses CVE-2016-6735
The device is affected if it runs Android 7.0 or earlier, contains an NVIDIA GPU, and lacks the November 2016 or later Android security patch that addresses this NVIDIA GPU driver vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided security patch or OTA update for Android that addresses CVE-2016-6735; devices already compromised may require reflashing the operating system.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6735 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data