dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-31614

HIGH · 7.8 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 11.8 / 13.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 contains a vulnerability in the Virtual GPU Manager (vGPU plugin) where it may double-free some resources. An attacker may exploit this vulnerability with other vulnerabilities to cause denial of service, code execution, and 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
How this class of weakness works · CWE-415

The same block of memory is freed twice, corrupting the allocator's bookkeeping in ways an attacker can shape toward code execution. It usually stems from tangled ownership of a pointer. The fix is clear, single ownership of each allocation and clearing pointers once they are freed.

General guidance for the double free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.0, < 11.8>= 13.0, < 13.3= 14.0= 14.1

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

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.8 / 13.3 or later
Fixed in 11.813.3
Vendor patch nvidia.custhelp.com →
Recommended fix High confidence

vGPU 11.8+ (11.x branch), vGPU 13.3+ (13.x branch), or vGPU 14.2+ (14.x branch)

  1. Check the current vGPU software version installed using NVIDIA vGPU software management tools or hypervisor commands
  2. Review the NVIDIA security bulletin at https://nvidia.custhelp.com/app/answers/detail/a_id/5383 for the complete list of fixed versions and download links
  3. For vGPU 11.x deployments: Upgrade to version 11.8 or later (e.g., 11.9, 12.x)
  4. For vGPU 13.x deployments: Upgrade to version 13.3 or later (e.g., 13.4, 14.x)
  5. For vGPU 14.0/14.1 deployments: Upgrade to version 14.2 or later
  6. Ensure the Virtual GPU Manager (vGPU plugin) is updated on the hypervisor host
  7. Reboot or restart vGPU services as required by the update process
  8. Verify the new version is correctly installed and vGPU functionality is operational
Caveat Verify hypervisor compatibility with the new vGPU version before upgrading; review NVIDIA's release notes for any configuration or migration requirements

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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