CVE-2024-0127 is a high-severity improper input validation vulnerability in the GPU kernel driver of NVIDIA vGPU Manager affecting NVIDIA vGPU software on all supported hypervisors. The flaw can be triggered by a guest OS user after compromise of the guest OS kernel, allowing malformed or otherwise unsafe input to reach the vGPU Manager GPU kernel driver without adequate validation. The vulnerability affects the virtualization boundary between a guest environment and the NVIDIA vGPU management stack and can result in multiple security impacts within the host or virtualization context.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability in NVIDIA vGPU Manager that allows a guest OS user to trigger improper input validation.
A high-severity NVIDIA vGPU Manager GPU kernel driver improper input validation issue that can be triggered by a guest OS user after compromising the guest OS kernel, potentially leading to code execution, privilege escalation, data tampering, DoS, and information disclosure.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.