dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-33219

HIGH · 7.8 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA Display Driver for Linux contains an integer overflow or wraparound vulnerability in the kernel mode component. When exploited, this could allow an attacker to trigger the overflow condition leading to potential code execution with kernel privileges, privilege escalation, data tampering, denial of service, or information disclosure.

MitigationApply the NVIDIA security update/patched display driver version once released. Prioritize systems with direct user access or exposure to untrusted graphics workloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if NVIDIA display driver is installed
    Run 'lsmod | grep nvidia' to list loaded NVIDIA kernel modules, or check /proc/driver/nvidia/version if it exists
    Affected if Any NVIDIA kernel module is loaded indicates the driver is installed
  2. Identify the installed NVIDIA driver version
    Read /proc/driver/nvidia/version or run 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' as root
    Affected if The displayed version number falls within the vulnerable range (compare to the fixed version once NVIDIA releases the patch)
  3. Verify the kernel mode component is active
    Check if nvidia.ko, nvidia_modeset.ko, or nvidia_uvm.ko kernel modules are loaded via 'lsmod | grep nvidia'
    Affected if The vulnerable kernel mode component is loaded and active
  4. Confirm Linux kernel is using the NVIDIA driver
    Run 'ls -la /dev/nvidia*' to list NVIDIA device nodes, or check dmesg for 'nvidia' kernel messages with 'dmesg | grep -i nvidia'
    Affected if NVIDIA device nodes exist or NVIDIA driver messages appear in kernel log, confirming the driver is in use

A system is affected if it runs a Linux NVIDIA display driver version within the vulnerable range with the kernel mode component loaded and active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA security update/patched display driver version once released. Prioritize systems with direct user access or exposure to untrusted graphics workloads.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33219 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data