dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-0127

HIGH · 7.8 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 →
80/100
Remediation priority · High
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 GPU kernel driver of the vGPU Manager for all supported hypervisors, where a user of the guest OS can cause an improper input validation by compromising the guest OS kernel. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, and information disclosure.

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 · moderate confidence

NVIDIA vGPU Manager contains an improper input validation vulnerability in its GPU kernel driver. An attacker who has already compromised the guest OS kernel can exploit this vulnerability to potentially achieve code execution, privilege escalation, data tampering, denial of service, or information disclosure. The vulnerability affects the vGPU Manager running on supported hypervisors.

MitigationApply the NVIDIA vGPU software patch or update to a version that addresses CVE-2024-0127. Ensure guest VM kernels are kept secure to reduce the likelihood of the prerequisite compromise needed to exploit this vulnerability.

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
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NVIDIA vGPU Manager is installed on the hypervisor
    Check for the presence of the vGPU Manager package or service. On Linux hypervisors, look for nvidia-vgpud or nvidia-vgpu-mgr packages or services. On Windows hypervisors, check for NVIDIA vGPU Manager in installed programs.
    Affected if vGPU Manager is present on the hypervisor system
  2. Determine the installed vGPU Manager version
    Run the appropriate command to query the vGPU Manager version. On Linux: dpkg -l | grep nvidia-vgpu or rpm -qa | grep vgpu. On Windows: Check the program version in Add/Remove Programs or via the NVIDIA vGPU software installer information.
    Affected if The installed version has not been patched to address CVE-2024-0127 (version comparison needed against NVIDIA's security bulletin)
  3. Verify if vGPU functionality is enabled and in use
    Check if any guest VMs are configured with vGPUs or if the hypervisor has vGPU resources allocated. On VMware: check VM settings for vGPU profiles. On other hypervisors: check vGPU configuration files or management interfaces.
    Affected if vGPU is enabled and guest VMs are using vGPU passthrough, as this indicates the vulnerable code path is active
  4. Confirm guest VM kernel compromise is a realistic threat
    Review guest VM security posture: check for unauthorized access, unusual processes, or indicators of kernel compromise in guest VMs that use vGPU.
    Affected if Guest VM kernels are compromised or at high risk of compromise, as this is the prerequisite condition for exploiting the vGPU Manager vulnerability

A user is affected if NVIDIA vGPU Manager is installed on their hypervisor and the version has not been updated to include the CVE-2024-0127 fix, especially when untrusted guest VMs have access to vGPU functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the NVIDIA vGPU software patch or update to a version that addresses CVE-2024-0127. Ensure guest VM kernels are kept secure to reduce the likelihood of the prerequisite compromise needed to exploit this vulnerability.

Recommended fix Moderate confidence

Obtain the fixed vGPU Manager version from NVIDIA's official security bulletin for CVE-2024-0127

  1. 1. Navigate to NVIDIA's official vGPU software support page at nvidia.custhelp.com to obtain the latest security patches
  2. 2. Locate the security bulletin or patch notes for CVE-2024-0127
  3. 3. Identify the specific vGPU Manager version applicable to your hypervisor (VMware ESXi, Microsoft Hyper-V, or KVM)
  4. 4. Download and install the patched vGPU Manager version for your hypervisor
  5. 5. Update the NVIDIA GPU drivers in the guest operating systems to match the new vGPU Manager version
  6. 6. Reboot the hypervisor and guest VMs as required by the update
Caveat Review NVIDIA's release notes for any compatibility changes between vGPU Manager and guest driver versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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