dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2023-0190

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 450.236.01 / 470.182.03 or later.
See remediation →
57/100
Remediation priority · Elevated
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 GPU Display Driver for Linux contains a vulnerability in the kernel mode layer, where a NULL pointer dereference may lead to denial of service.

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 GPU Display Driver for Linux contains a NULL pointer dereference vulnerability in the kernel mode layer. An attacker with local access could trigger this condition, causing a kernel panic or system crash resulting in denial of service.

MitigationApply the NVIDIA driver update containing the fix for CVE-2023-0190. In enterprise environments, test the patched driver thoroughly for GPU workload compatibility before production deployment.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gpu Display DriverApplication
Affected:>= 470, < 470.182.03>= 515, < 515.105.01>= 525, < 525.105.17>= 530, < 530.41.03>= 450, < 450.236.01

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm NVIDIA driver is installed
    Run 'lsmod | grep nvidia' to check if the NVIDIA kernel module is loaded, or check '/proc/driver/nvidia/version' for the driver version file.
    Affected if No NVIDIA driver is present, the system is not affected.
  2. Retrieve installed driver version
    Run 'nvidia-smi' and note the 'Driver Version' field, or read '/proc/driver/nvidia/version'.
    Affected if Unable to determine the driver version, manual inspection required.
  3. Compare version against affected ranges
    Check if the installed version falls within any of these ranges: 470.x.x to 470.182.02, 515.x.x to 515.105.00, 525.x.x to 525.105.16, 530.x.x to 530.41.02, or 450.x.x to 450.236.00.
    Affected if Installed version is less than the first fixed version in any of these ranges.
  4. Verify kernel module is loaded
    Confirm the nvidia kernel module is currently loaded in memory using 'lsmod | grep nvidia' and check module info with 'modinfo nvidia'.
    Affected if Module not loaded, the specific vulnerable code path may not be exercised.

The system is affected if an NVIDIA GPU display driver for Linux is installed and the driver version falls within any of the vulnerable version ranges listed, with the kernel module loaded.

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.

dbcve · scoped
Upgrade available Upgrade to 450.236.01 / 470.182.03 / 515.105.01 or later
Fixed in 450.236.01470.182.03515.105.01
Interim mitigation

Apply the NVIDIA driver update containing the fix for CVE-2023-0190. In enterprise environments, test the patched driver thoroughly for GPU workload compatibility before production deployment.

Recommended fix High confidence

470.182.03, 515.105.01, 525.105.17, or 530.41.03 (depending on your current branch)

  1. 1. Identify the currently installed NVIDIA driver version using 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. 2. Determine which driver branch (470, 515, 525, or 530) is currently in use
  3. 3. Download the appropriate fixed driver version from NVIDIA's official website or your Linux distribution's repository
  4. 4. For branch 470: upgrade to version 470.182.03 or later
  5. 5. For branch 515: upgrade to version 515.105.01 or later
  6. 6. For branch 525: upgrade to version 525.105.17 or later
  7. 7. For branch 530: upgrade to version 530.41.03 or later
  8. 8. Back up any critical data before performing the driver update
Caveat Driver updates may require kernel compatibility checks; ensure the new driver version is compatible with your running Linux kernel

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0190 — 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-2023-0190 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