dbcve.org
Virtual GpuApplication · Nvidia

CVE-2023-31026

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-02
Fix available
A fix is available. Upgrade to 13.9 / 15.4 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 vGPU software for Windows and Linux contains a vulnerability in the Virtual GPU Manager (vGPU plugin), 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 vGPU software contains a NULL-pointer dereference vulnerability in the Virtual GPU Manager's vGPU plugin. When triggered, this causes the vGPU Manager to crash, resulting in denial of service for all virtual machines relying on the affected vGPU resources.

MitigationApply the NVIDIA vGPU software security update (refer to NVIDIA's official advisory for the fixed version). Plan maintenance window as vGPU Manager restart may be required; test vGPU functionality and VM availability post-patch.

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:< 13.9>= 14.0, < 15.4>= 16.0, < 16.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. Check the installed NVIDIA vGPU Manager version on the hypervisor
    Run the hypervisor-specific command to retrieve the vGPU Manager package version. On VMware ESXi, use 'esxcli software vib list | grep -i nvidia' or check the NVIDIA VIB version. On Citrix XenServer, check the installed packages via 'rpm -qa | grep nvidia' or equivalent. On Microsoft Azure Stack HCI, use the relevant hypervisor management tool to view installed NVIDIA vGPU software components.
    Affected if The displayed version is < 13.9, OR >= 14.0 AND < 15.4, OR >= 16.0 AND < 16.2
  2. Confirm vGPU plugin is loaded and active
    Verify that the Virtual GPU Manager's vGPU plugin is loaded and running on the hypervisor host. Check hypervisor logs or use management tools to confirm the vGPU Manager service is operational and that vGPU-enabled VMs are present.
    Affected if The vGPU plugin is loaded and VMs are actively using vGPU resources from the Virtual GPU Manager
  3. Identify VMs using vGPU devices
    List all virtual machines configured with vGPU profiles or vGPU passthrough devices. This can be done via the hypervisor management interface (vSphere Client, XenCenter, etc.) or command-line tools that show VM hardware configuration.
    Affected if Any VMs are assigned vGPU profiles from the affected Virtual GPU Manager

The environment is affected if the NVIDIA vGPU Manager version falls within the vulnerable ranges and the vGPU plugin is actively providing graphics resources to virtual machines.

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 13.9 / 15.4 / 16.2 or later
Fixed in 13.915.416.2
Interim mitigation

Apply the NVIDIA vGPU software security update (refer to NVIDIA's official advisory for the fixed version). Plan maintenance window as vGPU Manager restart may be required; test vGPU functionality and VM availability post-patch.

Recommended fix Moderate confidence

NVIDIA vGPU software version 16.2 or later (or 15.4+ for 14.x-15.x branch, 13.9+ for 13.x branch)

  1. 1. Identify the currently installed NVIDIA vGPU software version using nvidia-smi or the vGPU Manager UI
  2. 2. Determine which version branch you are on (13.x, 14.x-15.x, or 16.x)
  3. 3. If on 13.x branch, upgrade to version 13.9 or later
  4. 4. If on 14.x-15.x branch, upgrade to version 15.4 or later
  5. 5. If on 16.x branch, upgrade to version 16.2 or later
  6. 6. Download the appropriate vGPU software package from the NVIDIA Licensing Portal or NVIDIA Enterprise website
  7. 7. Follow NVIDIA's standard vGPU software upgrade procedure, which typically involves: stopping virtual machines, uninstalling the current vGPU Manager, installing the new vGPU Manager, and rebooting the hypervisor
  8. 8. Verify the upgrade was successful by checking the vGPU Manager version and ensuring virtual machines can be restarted
Caveat Standard vGPU upgrade may require VM downtime; ensure proper backup and migration procedures are followed

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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