# CVE-2024-0074: CVE

> An attacker can trigger a buffer overflow in the NVIDIA GPU driver, causing denial of service and data tampering.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **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:** 27 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-0074, UBUNTU-CVE-2024-0074

## What is CVE-2024-0074?

CVE-2024-0074 is a high-severity memory corruption vulnerability in nvidia GPU Display driver, vGPU driver, Cloud Gaming driver, published on 27 Mar 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 Linux contains a vulnerability where an attacker may access a memory location after the end of the buffer. A successful exploit of this vulnerability may lead to denial of service and data tampering.

Weakness: CWE-788 (Access of Memory Location After End of Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2024-0074 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0074 is a high-severity memory corruption vulnerability in nvidia GPU Display driver, vGPU driver, Cloud Gaming driver, published on 27 Mar 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-0074 in the wild and no public exploit code.

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

## Sources

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

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