CVE-2021-1064
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 it obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer, which may lead to 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 confidenceNVIDIA vGPU manager contains a pointer dereference vulnerability in the vGPU plugin where an untrusted input value is converted to a pointer and dereferenced, potentially allowing an attacker to read arbitrary memory locations (information disclosure) or cause a crash (denial of service).
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
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Check if NVIDIA vGPU Manager is installedOn the hypervisor host, run: rpm -qa | grep -i nvidia-vgpu or lsmod | grep nvidia_vgpu (Linux) or check services in Windows hypervisorsAffected if vGPU Manager is not installed, the system is not affected by this specific vulnerability
-
Determine installed vGPU Manager versionRun: nvidia-smi -v or check the package version via rpm -qa | grep vgpu or check the installer version on the systemAffected if Version is >= 8.0 and < 8.6, OR >= 11.0 and < 11.3, then the system is vulnerable
-
Verify vGPU plugin is loaded/enabledCheck if vGPU is configured on any virtual machines: virsh list --all and virsh edit <vm_name> to check for vGPU device assignment, or check hypervisor documentation for vGPU enablement statusAffected if vGPU plugin is enabled and virtual machines have vGPU devices assigned, making the vulnerable code path accessible
-
Confirm hypervisor typeIdentify the hypervisor (VMware ESXi, Citrix XenServer, or Microsoft Windows Hyper-V) as vGPU Manager is specific to these platformsAffected if Hypervisor does not support NVIDIA vGPU, the vulnerability does not apply
System is affected if NVIDIA vGPU Manager is installed, running a version between 8.0-8.5 or 11.0-11.2, and vGPU functionality is enabled on the hypervisor.
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.x branches) to receive the patch for this vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1064 — 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-1064 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