dbcve.org
Virtual Gpu ManagerApplication · Nvidia

CVE-2021-1087

MEDIUM · 5.5 CVSS v3.1 Published 2021-04-29
Fix available
A fix is available. Upgrade to 8.7 / 11.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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 driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin), which could allow an attacker to retrieve information that could lead to a Address Space Layout Randomization (ASLR) bypass. This affects vGPU version 12.x (prior to 12.2), version 11.x (prior to 11.4) and version 8.x (prior to 8.7).

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 contains an information disclosure vulnerability in the vGPU plugin that allows an attacker to retrieve information leading to an ASLR bypass. This is a security weakness that leaks memory addresses or layout information, which can be chained with other exploits for privilege escalation.

MitigationUpgrade NVIDIA vGPU Manager to version 12.2, 11.4, or 8.7 (or later) depending on the branch in use.

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.7>= 11.0, < 11.4>= 12.0, < 12.2

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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, check for the presence of the vGPU Manager package. On Linux, this may appear as a package named 'nvidia-vgpu-manager', 'vgpu-manager', or similar. Run 'dpkg -l | grep vgpu' or 'rpm -qa | grep vgpu' to list installed vGPU packages.
    Affected if No vGPU Manager package is found, then this CVE does not apply to the environment.
  2. Determine installed vGPU Manager version
    Run the package query command from the previous step to obtain the exact version number. On some systems, 'nvidia-smi' or 'vgpu-manager --version' may also expose version information. Record the full version string (for example, 11.3.0 or 12.1.0).
    Affected if The version cannot be determined, assume the environment may be affected and treat as vulnerable.
  3. Confirm vGPU plugin is in use
    Check if any vGPU virtual machines or vGPU profiles are configured on the hypervisor. This typically involves querying the hypervisor's vGPU configuration. For example, on VMware this would be checking for vGPU-enabled VMs; on KVM, checking for vGPU device assignments. If no vGPU resources are configured, the plugin may not be active.
    Affected if vGPU plugin is actively being used (vGPU-enabled VMs exist), proceed to version comparison. If no vGPU resources are configured, the practical risk is lower but the software may still be vulnerable.
  4. Compare version against affected ranges
    Check if the installed version falls into any of these vulnerable ranges: 8.0 to 8.6 (inclusive), 11.0 to 11.3 (inclusive), or 12.0 to 12.1 (inclusive). If the version is 8.7 or higher, 11.4 or higher, or 12.2 or higher, it is NOT affected by this CVE.
    Affected if The installed version is less than 8.7, less than 11.4, or less than 12.2 (and at or above the minimum versions 8.0, 11.0, or 12.0 respectively), then the environment IS affected by CVE-2021-1087.

The environment is affected if NVIDIA vGPU Manager is installed, the vGPU plugin is in use, and the installed version falls below 8.7, 11.4, or 12.2 depending on the major branch.

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.7 / 11.4 / 12.2 or later
Fixed in 8.711.412.2
Interim mitigation

Upgrade NVIDIA vGPU Manager to version 12.2, 11.4, or 8.7 (or later) depending on the branch in use.

Fix this in Virtual Gpu Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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