{"uuid": "a2b6ef48-24a8-4e38-91e8-37645d27189e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-1075", "type": "seen", "source": "https://t.me/hacking_Attack/6646", "content": "Black Hat Ethical Hacking\nNvidia Warns: Severe Security Bugs in GPU Driver, vGPU Software\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Nvidia Warns: Severe Security Bugs in GPU Driver, vGPU SoftwarePost Views: 82 \nReading Time: 1 Minute\nNvidia has disclosed a group of security vulnerabilities in the Nvidia graphics processing unit (GPU) display driver, which could subject gamers and others to privilege-escalation attacks, arbitrary code execution, denial of service (DoS) and information disclosure.\nMeanwhile, the Nvidia virtual GPU (vGPU) software also has a group of bugs that could lead to a range of similar attacks. 5 GPU Display Driver Security BugsThe most severe of the five bugs in the GPU display driver is tracked as CVE-2021-1074, which rates 7.5 out of 10 on the CVSS vulnerability scale, making it high-severity. It exists in the display driver\u2019s installer, and allows an attacker with local system access to replace an application resource with malicious files. Such an attack may lead to code execution, escalation of privileges, denial of service, or information disclosure.\n\nAnother high-severity bug, CVE-2021-1075, rates 7.3 on the CVSS scale. NVIDIA Windows GPU Display Driver for Windows, all versions, contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape where the program dereferences a pointer that contains a location for memory that is no longer valid, which may lead to code execution, denial of service, or escalation of privileges.\nSee Also: Telegram Platform Abused in \u2018ToxicEye\u2019 Malware Campaigns\nTwo medium-severity flaws, CVE-2021-1076\u00a0and CVE-2021-1077, both rate 6.6 on the CVSS scale. The former NVIDIA GPU Display Driver for Windows and Linux, all versions, contains a vulnerability in the kernel mode layer (nvlddmkm.sys or nvidia.ko) where improper access control may lead to denial of service, information disclosure, or data corruption. The latter NVIDIA GPU Display Driver for Windows and Linux, R450 and R460 driver branch, contains a vulnerability where the software uses a reference count to manage a resource that is incorrectly updated, which may lead to denial of service.\n\nAnd finally, the medium-severity CVE-2021-1078\u00a0rates 5.5 on the CVSS scale and NVIDIA Windows GPU Display Driver for Windows, all versions, contains a vulnerability in the kernel driver (nvlddmkm.sys) where a NULL pointer dereference may lead to system crash. 8 Nvidia vGPU Software VulnerabilitiesMeanwhile, Nvidia\u2019s vGPU software has eight different security holes. The virtualized GPU allows computing acceleration tailored for resource-intensive workloads like graphics-rich virtual workstations, data science and artificial intelligence.\nSee Also: Offensive Security Tool: ADFSBrute\nThe first four bugs are high-severity input-validation bugs that can lead to information disclosure, data tampering or DoS.\n\nThese are:\n\n* CVE\u20112021\u20111080\u00a0(7.8 on the CVSS scale): A vulnerability in the vGPU Manager (vGPU plugin), in which certain input data is not validated;\n* CVE\u20112021\u20111081\u00a0(7.8): A vulnerability in the guest kernel mode driver and vGPU manager (vGPU plugin), in which an input length is not validated;\n* CVE\u20112021\u20111082\u00a0(7.8): A vulnerability in the vGPU Manager (vGPU plugin), stemming from an input length not being validated;\n* CVE\u20112021\u20111083\u00a0(7.8): A vulnerability in the guest kernel-mode driver and vGPU Manager (vGPU plugin), also arising from an input length not being validated.\nThe other four could lead to a variety of outcomes if exploited:\n\n* CVE\u20112021\u20111084\u00a0(7.8): A vulnerability in the guest kernel-mode driver and vGPU Manager (vGPU plugin), in which an input length is[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:03:20.418263Z"}