CVE-2021-1061
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 · uneditedNVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which a race condition may cause the vGPU plugin to continue using a previously validated resource that has since changed, which may lead to denial of service or information disclosure. 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 confidenceNVIDIA vGPU manager contains a race condition vulnerability in the vGPU plugin that allows continued use of resources that were previously validated but have since changed. This can lead to denial of service or information disclosure.
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>= 8.0, < 8.6>= 11.0, < 11.3CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NVIDIA vGPU Manager is installedCheck for vGPU manager packages or service. On Linux, run 'rpm -qa | grep -i vgpu' or 'dpkg -l | grep -i nvidia-vgpu' or check for the 'nvidia-vgpu' service with 'systemctl list-units | grep vgpu'. On Windows, check Programs and Features for NVIDIA vGPU Manager.Affected if NVIDIA vGPU Manager is present on the system
-
Identify the installed vGPU Manager versionRun 'nvidia-smi -q' or check the package version with 'rpm -q nvidia-vgpu-manager' (RHEL/CentOS) or 'dpkg -l nvidia-vgpu-manager' (Debian/Ubuntu). The version is typically displayed in the output.Affected if The installed version is greater than or equal to 8.0 but less than 8.6, OR greater than or equal to 11.0 but less than 11.3
-
Verify vGPU plugin is enabledCheck vGPU configuration files typically located in /etc/vgpu/ or /etc/nvidia/vgpu/. Look for enabled vGPU virtual machines or check the hypervisor configuration (e.g., for VMware: VM configuration settings, for KVM: libvirt domain XML). The vGPU plugin is active when any VM is assigned a vGPU passthrough device.Affected if vGPU plugin is enabled and at least one virtual machine is configured with a vGPU device
-
Check for vGPU resource assignment activityReview vGPU assignment logs or monitor ongoing vGPU resource usage. On hypervisors like KVM, check 'virsh list' for running VMs with vGPU attachments, or review /var/log/nvidia-vgpu.log if available. On VMware, check the VM summary tab for vGPU device presence.Affected if Any VMs are currently using vGPU passthrough devices from the vGPU Manager
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 the vGPU plugin is enabled with at least one virtual machine using vGPU resources.
Generated from the published advisory. Verify against your own configuration.
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 data8.611.3
Upgrade vGPU manager to version 8.6 or later (for 8.x branches) or version 11.3 or later (for 11.0 branch) to patch the race condition in the vGPU plugin.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-1061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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