dbcve.org
Virtual GpuApplication · Nvidia

CVE-2023-0183

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 the kernel mode layer where an out-of-bounds write can lead to denial of service 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 · high confidence

NVIDIA GPU Display Driver for Linux contains an out-of-bounds write vulnerability in the kernel mode layer. This memory corruption flaw can lead to denial of service (system crash/hang) and potential data tampering by allowing unauthorized memory writes outside allocated buffers.

MitigationApply the NVIDIA driver security update or patch that addresses CVE-2023-0183. This typically involves updating the NVIDIA GPU Display Driver to a patched version and may require system reboots for the kernel module to reload.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Identify if NVIDIA GPU driver is installed
    Run 'lsmod | grep nvidia' to check if the NVIDIA kernel module is loaded, or check for driver files in '/usr/src/nvidia-' directories
    Affected if No NVIDIA kernel module is loaded - the driver is not installed and this CVE does not apply
  2. Determine installed NVIDIA driver version
    Run 'cat /proc/driver/nvidia/version' or use 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' to get the driver version number
    Affected if Unable to determine version - the NVIDIA driver may not be properly installed
  3. Compare driver version against affected ranges
    The affected version ranges for Nvidia Virtual GPU are: < 11.12, >= 13.0 to < 13.7, and >= 15.0 to < 15.2. Check if your installed version falls into any of these ranges
    Affected if Your driver version is within < 11.12, >= 13.0 and < 13.7, or >= 15.0 and < 15.2 - you are likely affected by this CVE
  4. Verify the driver is running in kernel mode
    The vulnerability exists in the kernel mode layer (nvlddmkm). Confirm the driver is actively handling GPU operations by checking 'nvidia-smi' output and ensuring the kernel module is loaded
    Affected if The driver is loaded and actively handling GPU operations, and the version is in an affected range, the system is vulnerable

You are affected if the NVIDIA GPU driver for Linux is installed and the running version falls within < 11.12, >= 13.0 to < 13.7, or >= 15.0 to < 15.2, and the kernel mode driver is actively 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 security update or patch that addresses CVE-2023-0183. This typically involves updating the NVIDIA GPU Display Driver to a patched version and may require system reboots for the kernel module to reload.

Recommended fix Moderate confidence

NVIDIA GPU Display Driver 11.12 (or later for 11.x branch), 13.7 (or later for 13.x branch), or 15.2 (or later for 15.x branch)

  1. 1. Identify the currently installed NVIDIA GPU Display Driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. For Linux systems with driver branch 11.x: Upgrade to NVIDIA GPU Display Driver version 11.12 or later
  3. 3. For Linux systems with driver branch 13.x: Upgrade to NVIDIA GPU Display Driver version 13.7 or later
  4. 4. For Linux systems with driver branch 15.x: Upgrade to NVIDIA GPU Display Driver version 15.2 or later
  5. 5. Download the appropriate driver from the official NVIDIA website (nvidia.com) or your distribution's package repository
  6. 6. Install the new driver package following standard procedures (e.g., `sudo apt-get install nvidia-driver-<version>` on Debian/Ubuntu or `sudo yum install kmod-nvidia` on RHEL/CentOS)
  7. 7. Reboot the system to load the new kernel module: `sudo reboot`
  8. 8. Verify the installed version matches the target fixed version using `nvidia-smi`
Caveat Driver upgrades may require matching kernel version compatibility; review NVIDIA's driver release notes for kernel support before upgrading

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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