# CVE-2025-23332: Null dereference in GeForce

> An attacker can trigger a null pointer dereference in the NVIDIA Linux kernel module, causing a denial of service.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-23332, ECHO-03ce-ef79-5d82, GHSA-3cg3-jw2v-vmvx, UBUNTU-CVE-2025-23332

## What is CVE-2025-23332?

CVE-2025-23332 is a medium-severity vulnerability in NVIDIA GeForce, published on 23 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

NVIDIA Display Driver for Linux contains a vulnerability in a kernel module, where an attacker might be able to trigger a null pointer deference. A successful exploit of this vulnerability might lead to denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-23332?


## How do I fix CVE-2025-23332?

Apply the vendor's patch.

## Is CVE-2025-23332 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23332 and fix it if it is affected.

What it is: CVE-2025-23332 is a medium-severity vulnerability in NVIDIA GeForce, published on 23 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-23332 in the wild and no public exploit code.

Affected product: NVIDIA GeForce. 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-2025-23332/ (Markdown: https://insights.sbomify.com/CVE-2025-23332/index.md)
```

## Sources

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

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