# CVE-2025-33219: Integer overflow in GeForce

> An integer overflow in the NVIDIA Linux kernel module allows attackers to execute code, escalate privileges, or cause denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 28 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-33219, GHSA-h92q-fpwc-x9x5, UBUNTU-CVE-2025-33219

## What is CVE-2025-33219?

CVE-2025-33219 is a high-severity vulnerability in NVIDIA GeForce, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA Display Driver for Linux contains a vulnerability in the NVIDIA kernel module where an attacker could cause an integer overflow or wraparound. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, or information disclosure.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2025-33219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-33219 is a high-severity vulnerability in NVIDIA GeForce, published on 28 Jan 2026. 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-2025-33219 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-33219/ (Markdown: https://insights.sbomify.com/CVE-2025-33219/index.md)
```

## Sources

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

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