CVE-2021-1065
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 input data 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 manager contains an input validation vulnerability in the vGPU plugin. The lack of proper input validation allows malicious or malformed data to be processed, potentially 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 Manager is installedCheck for the presence of the vGPU Manager package on the hypervisor host. On Linux, this typically appears as an RPM/DEB package named nvidia-vgpu-manager or similar. Use 'rpm -qa | grep vgpu' or 'dpkg -l | grep vgpu' to list installed packages.Affected if The nvidia-vgpu-manager package is present on the system
-
Identify the installed vGPU Manager versionRun 'rpm -qi nvidia-vgpu-manager' or 'dpkg -s nvidia-vgpu-manager' to retrieve the installed version number. Alternatively, check /usr/share/nvidia/vgpu/ for version-related files.Affected if The displayed version falls within 8.0 to 8.5.x (for 8.x releases) or 11.0 to 11.2.x (for 11.x releases)
-
Verify vGPU plugin or component is in useConfirm that virtual GPU (vGPU) functionality is enabled on the hypervisor. Check for active vGPU-enabled VMs or vGPU profiles configured via virsh (for KVM) or VMware vSphere settings. Look for NVIDIA vGPU metadata or configuration files in the virtualization environment.Affected if vGPU profiles are configured and VMs are using virtual GPUs
-
Check hypervisor platformIdentify the underlying hypervisor (VMware ESXi, Citrix XenServer, or KVM/QEMU). The vGPU Manager installs differently per platform, so note which virtualization platform is in use.Affected if Running on VMware ESXi, Citrix XenServer, or KVM with NVIDIA vGPU support enabled
You are affected if NVIDIA vGPU Manager is installed with a version between 8.0 and 8.5.x (inclusive) or between 11.0 and 11.2.x (inclusive), AND vGPU functionality is actively configured or in use on your virtualization host.
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 NVIDIA vGPU manager to version 8.6 or later (for 8.x releases) or version 11.3 or later (for 11.0 releases) to address the input validation deficiency.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-1065 — 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-1065 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