# CVE-2016-6916: Integer overflow in n/a

> Local attackers can cause a system crash via an integer overflow in the NVIDIA video driver on Android devices.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qmh2-wxwc-w56h

## What is CVE-2016-6916?

CVE-2016-6916 is a high-severity vulnerability in n/a, published on 24 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer 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 allows local users to cause a denial of service (system crash) via unspecified vectors, which triggers a buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-6916?

It affects 4 products.


Products: Nvidia Shield Tablet Firmware, Nvidia Shield Tablet Tk1 Firmware, Nvidia Shield Tv Firmware, Nvidia Video Driver.

## How do I fix CVE-2016-6916?

No fix has been published for CVE-2016-6916 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6916 being exploited?

There is no known exploitation of CVE-2016-6916 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-6915](https://insights.sbomify.com/CVE-2016-6915/): Memory corruption in n/a (high 7.8)
- [CVE-2016-6917](https://insights.sbomify.com/CVE-2016-6917/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6916 and fix it if it is affected.

What it is: CVE-2016-6916 is a high-severity vulnerability in n/a, published on 24 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6916 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6916/ (Markdown: https://insights.sbomify.com/CVE-2016-6916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6916
- OSV: https://osv.dev/vulnerability/CVE-2016-6916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6916/
Summaries are generated and may contain mistakes; the official description above is the record.