CVE-2024-0146
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 software contains a vulnerability in the Virtual GPU Manager, where a malicious guest could cause memory corruption. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, or data tampering.
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 confidenceNVIDIA vGPU Virtual GPU Manager contains a memory corruption vulnerability that can be exploited by a malicious guest virtual machine. Successful exploitation may allow the attacker to execute code, cause denial of service, disclose information, or tamper with data on the host system.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify NVIDIA vGPU software is installedOn the hypervisor host, check for NVIDIA vGPU Virtual GPU Manager packages or services. On Linux, look for packages like 'nvidia-vgpu' or 'vgpu-manager' using package managers (dpkg -l, rpm -qa). On Windows, check Programs and Features or the NVIDIA licensing portal.Affected if NVIDIA vGPU Virtual GPU Manager software is present on the system
-
Identify the Virtual GPU Manager versionRun 'nvidia-smi' or check the vGPU Manager package version. On Linux: 'rpm -qa | grep vgpu' or 'dpkg -l | grep vgpu'. On Windows: check the installed version in Programs or the NVIDIA vGPU Manager service properties.Affected if The installed version matches a vulnerable release of the NVIDIA vGPU Virtual GPU Manager
-
Confirm the host is configured as a vGPU hypervisorCheck hypervisor configuration for vGPU-enabled VMs. On VMware: look for vGPU profiles assigned to VMs. On XenServer: check for vGPU-enabled VMs via xl or xe commands. On KVM: check for mdev or vGPU devices assigned to guest VMs.Affected if The host runs guest VMs with vGPU passthrough enabled, creating the attack surface for malicious guests
-
Check for active vGPU guest connectionsReview active guest VM sessions using the hypervisor management interface (vCenter, XenCenter, virsh) to identify which VMs have vGPU resources allocated.Affected if Untrusted or potentially malicious guest VMs have active vGPU allocations
-
Audit vGPU licensing statusVerify the NVIDIA vGPU licensing server configuration and license status using the NVIDIA License System or nvidia-smi -L output.Affected if The environment relies on NVIDIA vGPU licensing, which confirms vGPU Manager deployment
The environment is affected if NVIDIA vGPU Virtual GPU Manager is installed and running on the hypervisor host, enabling guest VMs to access vGPU resources.
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 dataApply the NVIDIA vGPU software update containing the fix for this vulnerability. Coordinate a maintenance window as updating the Virtual GPU Manager may require hypervisor updates and guest driver reinstallation.
- 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-2024-0146 — 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-2024-0146 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