dbcve.org
Virtual GpuApplication · Nvidia

CVE-2023-0187

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-01
Fix available
A fix is available. Upgrade to 11.12 / 13.7 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 Windows and Linux contains a vulnerability in the kernel mode layer handler, where an out-of-bounds read can 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 Windows and Linux contains an out-of-bounds read vulnerability in the kernel mode layer handler. This can allow an attacker to read unintended memory locations, potentially causing a denial of service condition.

MitigationApply the NVIDIA driver update/patch when available. Until patched, consider restricting untrusted access to GPU resources and monitoring for unusual driver behavior.

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
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. Identify if NVIDIA vGPU software is installed
    Run 'nvidia-smi' or check for the nvidia driver module. On Linux: 'lsmod | grep nvidia' or check '/proc/driver/nvidia/version'. On Windows: check Device Manager for NVIDIA GPU drivers.
    Affected if No NVIDIA driver or vGPU software is found - not applicable to this CVE.
  2. Determine the installed NVIDIA vGPU driver version
    Execute 'nvidia-smi' and note the 'Driver Version' field. On Linux, also check 'cat /proc/driver/nvidia/version'. For vGPU, check the hypervisor's vGPU manager version.
    Affected if Unable to determine version - may require manual inspection of installed packages.
  3. Compare the installed version against affected ranges
    Check if the driver version falls into any of these vulnerable ranges: versions before 11.12, versions 13.0-13.6, or versions 15.0-15.1. Note the exact version number from step 2 and compare.
    Affected if The installed version is 11.x before 11.12, OR 13.x between 13.0-13.6 inclusive, OR 15.x between 15.0-15.1 inclusive.
  4. Confirm kernel mode layer is in use
    Verify the system is using the NVIDIA kernel mode driver (nvlddmkm on Windows, nvidia on Linux). On Windows check Event Viewer for 'nvlddmkm' driver events. On Linux verify the nvidia kernel module is loaded via 'lsmod | grep nvidia'.
    Affected if The kernel mode nvidia driver is loaded and in use - required for this vulnerability to be exploitable.
  5. Check if vGPU or GPU passthrough is configured
    On the hypervisor (for vGPU), verify vGPU profiles are assigned. Check hypervisor documentation or run 'nvidia-smi -q' to see vGPU configuration details.
    Affected if The system uses vGPU or GPU passthrough with the vulnerable driver - this configuration exposes the kernel mode handler.

The environment is affected if NVIDIA vGPU software is installed with a driver version in the ranges before 11.12, 13.0-13.6, or 15.0-15.1, and the kernel mode driver is actively in use.

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 when available. Until patched, consider restricting untrusted access to GPU resources and monitoring for unusual driver behavior.

Recommended fix Moderate confidence

Virtual GPU 11.12, 13.7, or 15.2 (depending on your major version branch)

  1. Identify the currently installed NVIDIA Virtual GPU version using nvidia-smi or system documentation
  2. Determine which version range your current installation falls into: < 11.12, >=13.0 and <13.7, or >=15.0 and <15.2
  3. For Virtual GPU 11.x: Upgrade to version 11.12 or later
  4. For Virtual GPU 13.x: Upgrade to version 13.7 or later
  5. For Virtual GPU 15.x: Upgrade to version 15.2 or later
  6. Download the appropriate NVIDIA Virtual GPU software package from the NVIDIA licensing portal or official distribution channels
  7. Follow NVIDIA's standard Virtual GPU upgrade procedure: stop VM instances, update the hypervisor's vGPU software, restart VMs
  8. Verify the installed version matches the target fixed release using nvidia-smi
Caveat Review NVIDIA Virtual GPU release notes for your version branch to check for VM compatibility changes or feature modifications before upgrading

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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