# CVE-2024-0131: Denial of service in NVIDIA GPU Display Driver, vGPU software

> A user-mode attacker can cause a denial of service by reading a buffer with an incorrect length in the NVIDIA GPU kernel driver.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/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:** 2 Feb 2025
- **Updated:** 3 Feb 2025
- **Also known as:** DEBIAN-CVE-2024-0131, GHSA-5x4m-c6g6-r2qq, UBUNTU-CVE-2024-0131

## What is CVE-2024-0131?

CVE-2024-0131 is a medium-severity denial of service vulnerability in NVIDIA GPU Display Driver, vGPU software, published on 2 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA GPU kernel driver for Windows and Linux contains a vulnerability where a potential user-mode attacker could read  a buffer with an incorrect length. A successful exploit of this vulnerability might lead to denial of service.

Weakness: CWE-805 (Buffer Access with Incorrect Length Value)

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


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

Apply the vendor's patch.

## Is CVE-2024-0131 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0131 is a medium-severity denial of service vulnerability in NVIDIA GPU Display Driver, vGPU software, published on 2 Feb 2025. 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-0131 in the wild and no public exploit code.

Affected product: NVIDIA GPU Display Driver, vGPU software. 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-0131/ (Markdown: https://insights.sbomify.com/CVE-2024-0131/index.md)
```

## Sources

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

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