# CVE-2016-2557: Information disclosure in n/a

> Local attackers can exploit NVIDIA GPU driver flaws to read kernel memory, crash the system, or escalate privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-97mv-xw8f-5x6v

## What is CVE-2016-2557?

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

### Official description

The Escape interface in the Kernel Mode Driver layer in the NVIDIA GPU graphics driver R340 before 341.95 and R352 before 354.74 on Windows allows local users to obtain sensitive information from kernel memory, cause a denial of service (crash), or possibly gain privileges via unspecified vectors, which trigger uninitialized or out-of-bounds memory access.

Weakness: CWE-264

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

It affects 2 products.


Products: Nvidia Gpu Driver R340, Nvidia Gpu Driver R352.

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

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

## Is CVE-2016-2557 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2558](https://insights.sbomify.com/CVE-2016-2558/): Memory corruption in n/a (high 8.4)
- [CVE-2016-2556](https://insights.sbomify.com/CVE-2016-2556/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2557 is a high-severity vulnerability in n/a, published on 12 Apr 2016. 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-2557 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-2557/ (Markdown: https://insights.sbomify.com/CVE-2016-2557/index.md)
```

## Sources

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

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