dbcve.org
Virtual Gpu ManagerApplication · Nvidia

CVE-2021-1063

HIGH · 7.8 CVSS v3.1 Published 2021-01-08
Fix available
A fix is available. Upgrade to 8.6 / 11.3 or later.
See remediation →
80/100
Remediation priority · High
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 manager contains a vulnerability in the vGPU plugin, in which an input offset is not validated, which may lead to a buffer overread, which in turn may cause tampering of data, information disclosure, or denial of service. This affects vGPU version 8.x (prior to 8.6) and version 11.0 (prior to 11.3).

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 vGPU manager's vGPU plugin contains a buffer overread vulnerability caused by missing validation of an input offset. An attacker could manipulate this offset to read beyond buffer boundaries, potentially causing data tampering, information disclosure, or denial of service.

MitigationApply vendor patches by upgrading to vGPU version 8.6 or later, or version 11.3 or later, as indicated in NVIDIA's security bulletin.

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 Gpu ManagerApplication
Affected:>= 8.0, < 8.6>= 11.0, < 11.3

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

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. Verify NVIDIA vGPU Manager is installed
    On the hypervisor host (ESXi or KVM), check for the presence of the NVIDIA vGPU Manager package using system package management tools (e.g., rpm, dpkg, or ESXi viblist). Look for packages named nvidia-vgpu-manager, nvidia-vgpu, or similar vGPU-related packages.
    Affected if The vGPU Manager package is found on the system, indicating the vGPU plugin component is present.
  2. Retrieve the installed vGPU Manager version
    Query the installed package version using the appropriate package manager command (for example: rpm -q <package-name> on RHEL/CentOS, or esxcli software vib list | grep nvidia on ESXi). Note the full version number including minor version digits.
    Affected if A version number is returned, confirming vGPU Manager is installed as a software package.
  3. Confirm version falls within affected ranges
    Compare the installed version number against the affected ranges: versions 8.0 through 8.5 (inclusive), or versions 11.0 through 11.2 (inclusive). Check if the major version is 8 with minor version less than 6, or major version is 11 with minor version less than 3.
    Affected if The installed version is >= 8.0 and < 8.6, OR >= 11.0 and < 11.3, meaning the missing offset validation vulnerability is present in the vGPU plugin.
  4. Verify vGPU functionality is enabled
    Check hypervisor configuration for active vGPU virtual machines or vGPU profile assignments. On ESXi, use esxcli nvidia vgpu list or check VM configuration for vGPU device assignments. On KVM, check for vGPU mediated device allocations.
    Affected if vGPU profiles are assigned to virtual machines, meaning the vulnerable vGPU plugin code path is actively used.

A system is affected if NVIDIA vGPU Manager is installed with a version in the ranges 8.0 to 8.5 or 11.0 to 11.2, and vGPU functionality is enabled on the hypervisor.

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.

From vendor data
Upgrade available Upgrade to 8.6 / 11.3 or later
Fixed in 8.611.3
Interim mitigation

Apply vendor patches by upgrading to vGPU version 8.6 or later, or version 11.3 or later, as indicated in NVIDIA's security bulletin.

Fix this in Virtual Gpu Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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