dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-0128

HIGH · 7.1 CVSS v3.1 Published 2024-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 software contains a vulnerability in the Virtual GPU Manager that allows a user of the guest OS to access global resources. A successful exploit of this vulnerability might lead to information disclosure, data tampering, and escalation of privileges.

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 software contains a vulnerability in the Virtual GPU Manager where a user within the guest OS can access global resources that should be isolated. This represents a virtualization isolation bypass, potentially allowing information disclosure, data tampering, and privilege escalation.

MitigationApply the NVIDIA vGPU software update containing the fix for CVE-2024-0128 to the Virtual GPU Manager. Verify that guest VM isolation is properly enforced post-update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify NVIDIA vGPU software installation
    On the hypervisor host (VMware ESXi, Microsoft Hyper-V, or KVM), check for NVIDIA vGPU Manager package installation. For ESXi, run 'esxcli software vib list | grep -i nvidia' or check /opt/nvidia/ directory. For Hyper-V, check installed services or drivers. For KVM, check libvirt configuration and loaded NVIDIA kernel modules (lsmod | grep nvidia).
    Affected if NVIDIA vGPU Manager or related vGPU packages are found on the hypervisor host.
  2. Determine Virtual GPU Manager version
    For ESXi: run 'esxcli software vib list | grep -i vgpu' to get the exact version string (for example, NVIDIA-vGPU-16.x or similar naming pattern). For Hyper-V: check the installed NVIDIA vGPU software version via Add/Remove Programs or Get-Package. For KVM: check the installed nvidia-vgpu-manager package version via 'dpkg -l' or 'rpm -qa | grep nvidia'.
    Affected if The installed version matches or is earlier than the fixed version released by NVIDIA for CVE-2024-0128 (compare your version against NVIDIA's security bulletin).
  3. Verify vGPU is enabled on guest VMs
    Check the configuration of running guest VMs. For ESXi: use 'vmware -v' or check VMX configuration file for lines containing 'pciPassthru' or 'vgpu' configuration. For Hyper-V: check VM settings for GPU partitioning. For KVM: examine libvirt XML configuration (virsh edit <vmname>) for <hostdev> elements referencing NVIDIA vGPU devices.
    Affected if Any guest VM is configured with vGPU passthrough or GPU partitioning enabled.
  4. Confirm guest VM isolation status
    From within a guest OS, check if global GPU resources are accessible that should be isolated between VMs. This may require examining GPU memory allocation, checking for unexpected access to shared GPU buffers, or using NVIDIA tools within the guest to probe for cross-VM resource visibility (if available).
    Affected if Global GPU resources that should be isolated per-VM are accessible or visible from within a guest OS.

If NVIDIA vGPU software is installed with a version prior to the fix and vGPU passthrough is enabled on any guest VM, the environment is affected by this virtualization isolation bypass vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA vGPU software update containing the fix for CVE-2024-0128 to the Virtual GPU Manager. Verify that guest VM isolation is properly enforced post-update.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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