# CVE-2022-42264: Memory corruption in vGPU software (guest driver) - Linux, vGPU software (Virtual GPU Manager), NVIDIA Cloud Gaming (guest driver), NVIDIA Cloud Gaming (Virtual GPU Manager)

> An unprivileged user can exploit an out-of-range pointer offset in the NVIDIA Linux GPU driver to tamper with data, disclose information, or cause denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** Yes
- **Published:** 30 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-42264, UBUNTU-CVE-2022-42264

## What is CVE-2022-42264?

CVE-2022-42264 is a high-severity memory corruption vulnerability in Nvidia Gpu Display Driver, published on 30 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer, where an unprivileged regular user can cause the use of an out-of-range pointer offset, which may lead to data tampering, data loss, information disclosure, or denial of service.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-823 (Use of Out-of-range Pointer Offset)

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

It affects 3 products.


Products: Nvidia Cloud Gaming, Nvidia Gpu Display Driver, Nvidia Virtual Gpu.

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

Apply the vendor's patch.

## Is CVE-2022-42264 being exploited?

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

## Other vulnerabilities in Nvidia Gpu Display Driver

- [CVE-2022-34669](https://insights.sbomify.com/CVE-2022-34669/): Path traversal in vGPU software (guest driver) - Windows, NVIDIA Cloud Gaming (guest driver) (high 8.8)
- [CVE-2024-0107](https://insights.sbomify.com/CVE-2024-0107/): Memory corruption in GPU Display Driver, vGPU Software, Cloud Gaming (high 7.8)
- [CVE-2024-0084](https://insights.sbomify.com/CVE-2024-0084/): CVE (high 7.8)
- [CVE-2024-0089](https://insights.sbomify.com/CVE-2024-0089/): CVE (high 7.8)
- [CVE-2024-0090](https://insights.sbomify.com/CVE-2024-0090/): CVE (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42264 is a high-severity memory corruption vulnerability in Nvidia Gpu Display Driver, published on 30 Dec 2022. 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-2022-42264 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-42264/ (Markdown: https://insights.sbomify.com/CVE-2022-42264/index.md)
```

## Sources

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

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