# CVE-2024-53869: Information disclosure in NVIDIA GPU Display Driver, vGPU software

> An attacker can leak uninitialized memory via the NVIDIA Unified Memory driver, leading to information disclosure.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 28 Jan 2025
- **Updated:** 28 Jan 2025
- **Also known as:** DEBIAN-CVE-2024-53869, GHSA-j688-f63h-5495, UBUNTU-CVE-2024-53869

## What is CVE-2024-53869?

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

### Official description

NVIDIA Unified Memory driver for Linux contains a vulnerability where an attacker could leak uninitialized memory. A successful exploit of this vulnerability might lead to information disclosure.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

Apply the vendor's patch.

## Is CVE-2024-53869 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53869 is a medium-severity vulnerability in NVIDIA GPU Display Driver, vGPU software, published on 28 Jan 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-53869 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-53869/ (Markdown: https://insights.sbomify.com/CVE-2024-53869/index.md)
```

## Sources

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

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