# CVE-2022-28182: Memory corruption in NVIDIA GPU Display Driver

> An attacker can trigger an out-of-bounds write in the NVIDIA GPU driver via a crafted shader, leading to code execution and privilege escalation.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-ww5v-8cqx-53r8, UBUNTU-CVE-2022-28182

## What is CVE-2022-28182?

CVE-2022-28182 is a high-severity memory corruption vulnerability in Nvidia Gpu Display Driver, published on 17 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NVIDIA GPU Display Driver for Windows contains a vulnerability in the DirectX11 user mode driver (nvwgf2um/x.dll), where an unauthorized attacker on the network can cause an out-of-bounds write through a specially crafted shader, which may lead to code execution to cause denial of service, escalation of privileges, information disclosure, and data tampering. The scope of the impact may extend to other components.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-28182?

It affects 2 products.


Products: Nvidia Gpu Display Driver, Nvidia Virtual Gpu.

## How do I fix CVE-2022-28182?

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

## Is CVE-2022-28182 being exploited?

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

## Other vulnerabilities in Nvidia Gpu Display Driver

- [CVE-2026-24187](https://insights.sbomify.com/CVE-2026-24187/): Use after free in GeForce (high 8.8)
- [CVE-2023-0184](https://insights.sbomify.com/CVE-2023-0184/): Privilege escalation in NVIDIA GPU Display Driver (high 8.8)
- [CVE-2022-34671](https://insights.sbomify.com/CVE-2022-34671/): Memory corruption in NVIDIA GPU Display Driver for Windows (high 8.5)
- [CVE-2022-28181](https://insights.sbomify.com/CVE-2022-28181/): Memory corruption in NVIDIA GPU Display Driver (high 8.5)
- [CVE-2026-24190](https://insights.sbomify.com/CVE-2026-24190/): Privilege escalation in GeForce (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28182 and fix it if it is affected.

What it is: CVE-2022-28182 is a high-severity memory corruption vulnerability in Nvidia Gpu Display Driver, published on 17 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28182 in the wild and no public exploit code.

Affected product: Nvidia Gpu Display Driver. 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-2022-28182/ (Markdown: https://insights.sbomify.com/CVE-2022-28182/index.md)
```

## Sources

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

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