Guest-triggered code execution via manager memory corruption
Published Jan 28, 2025 · Updated Jan 28, 2025
Memory corruption in NVIDIA vGPU Software R530 and R535 allows guest OS users to execute code or crash the Virtual GPU Manager. A malicious guest can corrupt memory in the hypervisor-hosted manager, but NVIDIA has not disclosed the affected operation or input-validation failure. Access to a vGPU-enabled guest is required; successful exploitation can execute code, expose or alter data, or interrupt the host service.
Summary
What happened
Memory corruption in NVIDIA vGPU Software R530 and R535 allows guest OS users to execute code or crash the Virtual GPU Manager. A malicious guest can corrupt memory in the hypervisor-hosted manager, but NVIDIA has not disclosed the affected operation or input-validation failure. Access to a vGPU-enabled guest is required; successful exploitation can execute code, expose or alter data, or interrupt the host service.
The record
- CVE
- CVE-2024-0146
- Published
- Jan 28, 2025
- Updated
- Jan 28, 2025
- Vendor
- DPDK Project
- Product
- NVIDIA vGPU Software
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2025CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=R530, R535
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo