dbcve.org
Virtual GpuApplication · Nvidia

CVE-2023-0180

HIGH · 7.1 CVSS v3.1 Published 2023-04-01
Fix available
A fix is available. Upgrade to 11.12 / 13.7 or later.
See remediation →
73/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 a kernel mode layer handler, which may lead to 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 GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler that can be exploited to cause denial of service or allow information disclosure. Since the vulnerability exists in a kernel mode component, successful exploitation could grant access to sensitive system resources or cause system instability.

MitigationApply the NVIDIA driver update/patch provided by NVIDIA to address this kernel mode layer handler vulnerability. Update to a patched version of the NVIDIA GPU Display Driver for Linux.

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
Virtual GpuApplication
Affected:< 11.12>= 13.0, < 13.7>= 15.0, < 15.2

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Check if NVIDIA GPU driver is installed
    Run 'lsmod | grep nvidia' to list loaded NVIDIA kernel modules, or check for nvidia-smi at /usr/bin/nvidia-smi
    Affected if No NVIDIA kernel modules loaded or nvidia-smi not found means the driver is not installed and this CVE does not apply
  2. Identify the NVIDIA driver version
    Execute '/usr/bin/nvidia-smi' and note the 'Driver Version' field in the output, or run 'cat /proc/driver/nvidia/version'
    Affected if The displayed driver version falls within an affected range: < 11.12, >= 13.0 and < 13.7, or >= 15.0 and < 15.2
  3. Confirm NVIDIA Virtual GPU (vGPU) software is in use
    Check if the system is running a vGPU instance: look for nvidia-vgpud or nvidia-vgpu-mgr processes via 'ps aux | grep -i vgpu', or check /sys/drivers/nvidia/vgpu/ for vgpu presence
    Affected if This CVE specifically targets Nvidia Virtual GPU products; if vGPU software is NOT present, the system may not be affected regardless of driver version
  4. Verify kernel mode components are active
    Check loaded kernel modules with 'lsmod | grep nvidia' and verify nvlddmkm or nvidia_uvm modules are loaded
    Affected if The kernel mode layer handler vulnerability only applies when the nvidia kernel mode components are actively running; if no kernel modules are loaded despite driver installation, the vulnerable code path may not be exercised

The system is affected by CVE-2023-0180 if it runs Nvidia Virtual GPU software with a driver version matching < 11.12, >= 13.0 to < 13.7, or >= 15.0 to < 15.2 and has NVIDIA kernel mode modules 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 11.12 / 13.7 / 15.2 or later
Fixed in 11.1213.715.2
Interim mitigation

Apply the NVIDIA driver update/patch provided by NVIDIA to address this kernel mode layer handler vulnerability. Update to a patched version of the NVIDIA GPU Display Driver for Linux.

Recommended fix High confidence

15.2 (or 13.7 or 11.12 depending on your current branch - upgrade to the first fixed version in your branch: 11.12, 13.7, or 15.2)

  1. Identify the currently installed NVIDIA Virtual GPU driver version using 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. Determine which version branch you are on (11.x, 13.x, or 15.x)
  3. For versions < 11.12: Upgrade to version 11.12 or later
  4. For versions >= 13.0 and < 13.7: Upgrade to version 13.7 or later
  5. For versions >= 15.0 and < 15.2: Upgrade to version 15.2 or later
  6. Download the appropriate NVIDIA Virtual GPU software from nvidia.com or your enterprise software repository
  7. Install the new driver package following NVIDIA's standard installation procedure for your Linux distribution
  8. Reboot the system to load the new kernel module
Caveat Standard NVIDIA driver upgrade risks apply - test in non-production environment first, ensure compatibility with your hypervisor and guest VM configurations

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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