CVE-2024-0099
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 for Linux contains a vulnerability in the Virtual GPU Manager, where the guest OS could cause buffer overrun in the host. A successful exploit of this vulnerability might lead to information disclosure, data tampering, escalation of privileges, and denial of service.
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 software for Linux contains a buffer overrun vulnerability in the Virtual GPU Manager component. A malicious guest OS can exploit this to cause a buffer overrun on the host system, potentially achieving information disclosure, data tampering, privilege escalation, or denial of service.
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.
-
Identify NVIDIA vGPU software installationOn the Linux host, search for vGPU Manager packages or drivers. Common paths: /usr/src/nvidia-vgpu* or check installed packages with 'dpkg -l | grep nvidia' or 'rpm -qa | grep nvidia'. Also check for the nvidia-vgpu-mgr service.Affected if NVIDIA vGPU software (Virtual GPU Manager) is installed on the system.
-
Determine Virtual GPU Manager versionRun 'cat /sys/module/nvidia_vgpu_vfio/version' or check the nvidia-vgpu-mgr service version with 'nvidia-vgpu-mgr --version' if available. The version is typically embedded in the module or driver package name.Affected if The installed version is lower than the patched version for CVE-2024-0099 (compare against NVIDIA security bulletin).
-
Verify vGPU host configurationConfirm the host is configured to assign virtual GPUs to guest VMs. Check for active vGPU device assignments via 'virsh list --all' combined with 'ls -la /etc/vgpu.cfg' or similar vGPU configuration files in /etc or /var. Also check 'lspci | grep -i nvidia' for vGPU-enabled GPU devices.Affected if The host has active vGPU assignments to guest virtual machines, making it vulnerable to a malicious guest exploit.
-
Review vGPU activity logsExamine system logs for vGPU-related entries. Check /var/log/messages, /var/log/syslog, or journalctl output for 'nvidia-vgpu', 'vgpu', or 'NVIDIA' related events. Look for unexpected errors, buffer overflow messages, or unusual guest VM vGPU usage patterns.Affected if Logs show anomalous vGPU activity, error messages indicating buffer issues, or unexpected vGPU resource consumption by guest VMs.
A system is affected if it runs NVIDIA vGPU software for Linux with Virtual GPU Manager installed and configured to assign vGPUs to guest VMs, with a version below the patched release for CVE-2024-0099.
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 security update (if available) to patch the Virtual GPU Manager component. Until a patch is released, restrict trusted guest VM assignments and monitor for anomalous vGPU activity.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0099 — 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-0099 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