CVE-2021-1060
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 software contains a vulnerability in the guest kernel mode driver and vGPU plugin, in which an input index is not validated, which may lead to tampering of data 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 confidenceNVIDIA vGPU software contains an input validation vulnerability in the guest kernel mode driver and vGPU plugin where input indexes are not properly validated. This lack of bounds checking or validation could allow an attacker to manipulate memory references via crafted index values, leading to data tampering or denial of service conditions.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NVIDIA vGPU software is in useIdentify if the environment uses NVIDIA Virtual GPU (vGPU) software. This applies to virtualized hypervisors (VMware ESXi, Microsoft Hyper-V, Citrix XenServer, KVM) with GPU virtualization enabled. Check for vGPU profiles configured on VMs or GPU passthrough configurations that use vGPU software.Affected if The system does not use NVIDIA vGPU software - the vulnerability only affects the vGPU Manager and guest vGPU drivers, not standalone GPU drivers
-
Determine the installed vGPU Manager versionQuery the hypervisor for the installed NVIDIA Virtual GPU Manager version. On VMware ESXi, use 'esxcli software vib list | grep nvidia' or check via vSphere Client. On other hypervisors, check the installed vGPU Manager package or driver version. The version is typically displayed as major.minor (e.g., 8.5, 11.2).Affected if Unable to retrieve the vGPU Manager version - the software may not be installed or accessible for version checking
-
Compare version against affected rangesCompare the installed vGPU Manager version to the affected ranges: 8.0 <= version < 8.6 OR 11.0 <= version < 11.3. Any version in these ranges is vulnerable.Affected if The installed version is 8.0 through 8.5.x OR 11.0 through 11.2.x (the version falls within either of the two affected ranges)
You are affected if your hypervisor runs NVIDIA vGPU Manager with a version between 8.0-8.5 or 11.0-11.2, where the guest kernel mode driver and vGPU plugin process unvalidated input indexes.
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
Apply vendor patches by updating NVIDIA vGPU software to version 8.6 or later for the 8.x branch, or version 11.3 or later for the 11.x branch.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1060 — 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-1060 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