dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2023-0184

HIGH · 7.8 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 450.236.01 / 454.14 or later.
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 GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer handler which may lead to denial of service, escalation of privileges, information disclosure, and data tampering.

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 contains a kernel mode layer handler vulnerability affecting Windows and Linux that may lead to denial of service, privilege escalation, information disclosure, or data tampering. The flaw exists in the kernel-mode component of the display driver, likely involving improper input validation or boundary handling in a handler function.

MitigationApply the vendor-supplied NVIDIA GPU driver update (patch) to address the kernel mode layer handler vulnerability. Prioritize patching on systems with elevated privileges or exposure to untrusted GPU workloads.

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>= 450, < 454.14>= 470, < 474.30>= 515, < 518.03>= 525, < 528.89>= 530, < 531.41

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 NVIDIA driver version on Linux
    Run `nvidia-smi` or `cat /proc/driver/nvidia/version` to display the installed driver version
    Affected if The reported version falls within any of the affected ranges: 470.x to 470.182.02, 515.x to 515.105.00, 525.x to 525.105.16, 530.x to 530.41.02, 450.x to 450.236.00, 450.x to 454.13, 470.x to 474.29, 515.x to 518.02, 525.x to 528.88, or 530.x to 531.40
  2. Check NVIDIA driver version on Windows
    Run `nvidia-smi` from an elevated command prompt, or open Device Manager, expand 'Display adapters', right-click the NVIDIA GPU, select 'Properties', and view the Driver version
    Affected if The reported version falls within any of the affected ranges listed above
  3. Identify the specific driver branch family
    Examine the first three digits of the driver version (e.g., 470, 515, 525, 530, 450) to determine which version range applies to your installation
    Affected if The driver belongs to one of the affected branches (450, 470, 515, 525, or 530) AND its specific version is below the patched release for that branch
  4. Confirm the display driver kernel component is loaded
    On Linux, verify the nvidia kernel module is loaded via `lsmod | grep nvidia`; on Windows, confirm the display driver is installed and active in Device Manager
    Affected if The driver is loaded and the version falls within any affected range, indicating potential exposure to the kernel mode handler vulnerability

A system is affected if the installed NVIDIA GPU display driver version matches any of the vulnerable version ranges and the kernel mode driver component is 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.

dbcve · scoped
Upgrade available Upgrade to 450.236.01 / 454.14 / 470.182.03 or later
Fixed in 450.236.01454.14470.182.03
Interim mitigation

Apply the vendor-supplied NVIDIA GPU driver update (patch) to address the kernel mode layer handler vulnerability. Prioritize patching on systems with elevated privileges or exposure to untrusted GPU workloads.

Recommended fix High confidence

470.182.03 (or later for 470xx branch), 515.105.01 (or later for 515xx branch), 525.105.17 (or later for 525xx branch), or 530.41.03 (or later for 530xx branch)

  1. Identify the currently installed NVIDIA driver version using 'nvidia-smi' or 'cat /proc/driver/nvidia/version'
  2. Download the appropriate fixed driver version from NVIDIA's official website (nvidia.com) or your distribution's package repository
  3. For Linux: Stop the display manager (e.g., 'sudo systemctl stop gdm' or 'sudo service lightdm stop'), then install the new driver package
  4. For Linux: Run 'sudo apt-get install nvidia-driver-<version>' (Debian/Ubuntu) or 'sudo yum install nvidia-driver-<version>' (RHEL/CentOS) or use the downloaded .run installer
  5. Reboot the system after installation completes
  6. Verify the new version is installed using 'nvidia-smi' or checking '/proc/driver/nvidia/version'
Caveat Driver update requires system reboot; ensure to schedule maintenance window and back up any critical data

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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