NVIDIA GPU driver vulnerabilities
7 known CVE vulnerabilities in NVIDIA GPU driver, translated and rated.
- CVE-2017-6264High
An elevation of privilege vulnerability exists in the NVIDIA GPU driver (gm20b_clk_throt_set_cdev_state), where an out of bound memory read used as a function pointer could lead to code execution in the kernel. This issue is rated as high because it could allow a local malicious application to execute arbitrary code within the context of a privileged process.
- CVE-2017-0429High
CVE-2017-0429 describes an elevation of privilege vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.
- CVE-2016-8449High
CVE-2016-8449 is a privilege escalation vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as High because it requires compromising a privileged process first.
- CVE-2016-8435High
CVE-2016-8435 is a privilege escalation vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.
- CVE-2016-8430High
CVE-2016-8430 is a privilege escalation vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.
- CVE-2016-8428High
CVE-2016-8428 is a privilege escalation vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.
- CVE-2016-6775High
CVE-2016-6775 is a vulnerability in the NVIDIA GPU driver that allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.

