Host crash via kernel null dereference
Published Mar 12, 2020 · Updated Aug 4, 2024
A NULL pointer dereference in NVIDIA Virtual GPU Manager 10.1 and earlier allows local users to crash the hypervisor host through nvidia.ko. The nvidia.ko kernel module dereferences a null pointer, but NVIDIA has not disclosed the triggering input or execution path. Exploitation requires low-privileged local access to a supported hypervisor host and interrupts host availability without reported data access or modification.
Summary
What happened
A NULL pointer dereference in NVIDIA Virtual GPU Manager 10.1 and earlier allows local users to crash the hypervisor host through nvidia.ko. The nvidia.ko kernel module dereferences a null pointer, but NVIDIA has not disclosed the triggering input or execution path. Exploitation requires low-privileged local access to a supported hypervisor host and interrupts host availability without reported data access or modification.
The record
- CVE
- CVE-2020-5960
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA GPU Display Driver
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=ALL
What conditions does exploitation require?
What is affected?
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.
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