CVE-2016-6915
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 · uneditedStack-based buffer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before OTA 4.4, and Shield Table TK1 before OTA 1.5.
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 stack-based buffer overflow vulnerability exists in nvhost_job.c within the NVIDIA video driver for Android on Shield devices. The overflow occurs when processing video job submissions, potentially allowing a local attacker to execute arbitrary code or cause a denial of service.
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<= 4.3.0<= 1.4.0<= 3.2all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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.
-
Identify Shield device modelCheck device model via Settings > About device > Model number, or run 'getprop ro.product.model' via ADBAffected if Device is not a Shield Tablet, Shield Tablet Tk1, or Shield TV (this CVE applies only to these specific devices)
-
Check Shield Tablet firmware versionFor Shield Tablet: go to Settings > About device > Build number, or run 'getprop ro.build.version.release' via ADB. Compare against affected version <= 4.3.0Affected if Firmware version is 4.3.0 or lower on Shield Tablet
-
Check Shield Tablet Tk1 firmware versionFor Shield Tablet Tk1: go to Settings > About device > Build number, or run 'getprop ro.build.version.release' via ADB. Compare against affected version <= 1.4.0Affected if Firmware version is 1.4.0 or lower on Shield Tablet Tk1
-
Check Shield TV firmware versionFor Shield TV: go to Settings > About device > Build number, or run 'getprop ro.build.version.release' via ADB. Compare against affected version <= 3.2Affected if Firmware version is 3.2 or lower on Shield TV
User is affected if they own a Shield Tablet (firmware <= 4.3.0), Shield Tablet Tk1 (firmware <= 1.4.0), or Shield TV (firmware <= 3.2) and are running the vulnerable NVIDIA video driver.
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 appropriate OTA firmware update (Shield TV OTA 3.3+, Shield Table OTA 4.4+, Shield Table TK1 OTA 1.5+) to patch the vulnerable driver. Until updates are applied, minimize exposure by avoiding untrusted applications.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6915 — 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-6915 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