# CVE-2024-0126: Privilege escalation in GPU, vGPU, and Cloud Gaming

> A privileged attacker can exploit the NVIDIA GPU driver to escalate permissions, leading to code execution and data tampering.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Oct 2024
- **Updated:** 1 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-0126, GHSA-9gx5-phw8-cmrj, UBUNTU-CVE-2024-0126

## What is CVE-2024-0126?

CVE-2024-0126 is a high-severity vulnerability in NVIDIA GPU, vGPU, and Cloud Gaming, published on 26 Oct 2024. 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 Windows and Linux contains a vulnerability which could allow a privileged attacker to escalate permissions. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-0126?


## How do I fix CVE-2024-0126?

Apply the vendor's patch.

## Is CVE-2024-0126 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0126 and fix it if it is affected.

What it is: CVE-2024-0126 is a high-severity vulnerability in NVIDIA GPU, vGPU, and Cloud Gaming, published on 26 Oct 2024. 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-2024-0126 in the wild and no public exploit code.

Affected product: NVIDIA GPU, vGPU, and Cloud Gaming. 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-2024-0126/ (Markdown: https://insights.sbomify.com/CVE-2024-0126/index.md)
```

## Sources

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

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