Loading story…
NVIDIA released fixes for several high-severity vulnerabilities across its Windows and Linux display drivers, installers, and virtual GPU stack that could let attackers escalate privileges, corrupt memory, crash systems, or access sensitive data. The disclosed issues include CVE-2025-23277, an out-of-bounds kernel memory access flaw in NVIDIA Display Drivers for Windows and Linux; CVE-2025-23281, a Windows driver use-after-free tied to concurrent memory handling; CVE-2025-23276, a Windows installer access-control weakness that can yield administrator-level code execution during installation or update; and CVE-2025-23279, a TOCTOU race condition in the Linux and Solaris .run installer that can allow arbitrary code execution as root.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
7 events from the most recent confirmed update back to the earliest known activity.
On June 15, 2026, LevelBlue published an analysis of NVIDIA's Windows kernel display driver fixes, detailing systemic validation flaws across 14 IOCTL handlers and examining CVE-2026-24190, CVE-2026-24182, and CVE-2026-24193. The report recommended upgrading drivers, enforcing Microsoft driver blocklists, monitoring IOCTL activity, and restricting container access to GPU interfaces.
By May 2026, NVIDIA had released patched Windows Kernel Core Display Driver build 596.36. According to LevelBlue's analysis, this build introduced fixes across 35 examined functions, including 19 security-critical changes affecting IOCTL validation, privilege escalation, denial of service, and out-of-bounds write risks.
LevelBlue identified NVIDIA Windows Kernel Core Display Driver build 596.21, dated April 16, 2026, as the vulnerable build used in its analysis of later-fixed kernel flaws. The report ties this build to issues including CVE-2026-24190 and CVE-2026-24182.
NVIDIA released security updates for several vulnerabilities affecting display drivers and virtual GPU software, including CVE-2025-23277, CVE-2025-23281, and CVE-2025-23283. The fixes covered multiple Windows, Linux, guest vGPU, and Virtual GPU Manager branches and platforms.
NVIDIA disclosed CVE-2025-23279 in its July 2025 security bulletin as a local privilege escalation race condition in the .run installer for Linux and Solaris GPU drivers. The company released a fix in its July 2025 security update by adding proper synchronization and advised users to update to the latest GPU Display Driver versions.
NVIDIA remediated CVE-2025-23276, a local privilege escalation flaw in the Windows installer caused by improper access control over installer-created or modified files and directories. NVIDIA advised upgrading to fixed driver branches including R575 577.00+, R570 573.48+, R535 539.41+, and vGPU 18.4 or 16.11 or later.
Qualcomm addressed CVE-2025-27051, a double-free vulnerability in its Windows WLAN Host driver, in its July 2025 Security Bulletin. The flaw could cause severe memory corruption and potentially enable privilege escalation or arbitrary code execution on affected Windows systems using Qualcomm wireless chipsets.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
7 references tracked. Mallory keeps watching after this page renders.
levelblue.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcezeropath.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
NVIDIA has disclosed a high-severity vulnerability in its Display Driver, identified as CVE-2025-23309, which involves an uncontrolled DLL loading path. This flaw could allow attackers to cause arbitrary denial of service, escalate privileges, execute code, or tamper with data on affected systems. The vulnerability is not remotely exploitable, indicating that an attacker would require local access to exploit the issue. According to the official CVE entry, the vulnerability was published on October 10, 2025, and is being tracked by NVIDIA’s Product Security Incident Response Team (PSIRT). While the specific affected product versions are not listed in the CVE feed, the issue is confirmed to impact NVIDIA Display Driver software. In parallel, security reports highlight that NVIDIA has released patches addressing multiple high-severity vulnerabilities in its GPU drivers, some of which risk remote code execution (RCE) and privilege escalation. These patches are part of NVIDIA’s ongoing efforts to mitigate risks associated with their graphics drivers, which are widely used in both consumer and enterprise environments. The vulnerabilities addressed in the latest update could potentially be leveraged by attackers to gain unauthorized access or control over systems running vulnerable driver versions. Organizations using NVIDIA GPU drivers are strongly advised to review the latest security advisories and apply the recommended patches to reduce exposure. The disclosure underscores the importance of maintaining up-to-date drivers, as vulnerabilities in such low-level system components can have significant security implications. Security teams should also monitor for any signs of exploitation attempts targeting these flaws, especially in environments where local access by untrusted users is possible. The high CVSS score of 8.2 for CVE-2025-23309 reflects the potential impact of successful exploitation. NVIDIA’s prompt response and patch release demonstrate the company’s commitment to addressing security issues in its products. Enterprises should ensure that their asset inventories accurately reflect the presence of NVIDIA drivers and prioritize patching accordingly. The incident also highlights the broader trend of attackers targeting device drivers as a means to bypass operating system security controls. Given the critical role of GPU drivers in system performance and security, timely remediation is essential to prevent potential compromise. Security advisories from both NVIDIA and independent security researchers provide detailed guidance on mitigation steps. Regular vulnerability management processes should incorporate driver updates as a key component of endpoint security. Finally, organizations should consider implementing additional controls, such as application whitelisting and user privilege restrictions, to further reduce the risk of exploitation.
Jun 29, 2026
NVIDIA issued security updates for multiple products across its AI and enterprise software stack, fixing vulnerabilities that could allow **remote code execution**, denial of service, privilege escalation, data tampering, and information disclosure. The most severe issue disclosed in its broader March advisories was `CVE-2025-33244` in **NVIDIA Apex**, a widely used PyTorch extension for mixed-precision and distributed training. High-severity flaws were also addressed in **Triton Inference Server**, **Megatron LM**, **NeMo Framework**, and **Model Optimizer**, with NVIDIA warning that exploitation could disrupt AI workloads, expose sensitive training data, or enable unauthorized access. Medium-severity issues were additionally listed in **VIRTIO-Net**, **SNAP4**, and **B300 MCU**. NVIDIA later released urgent fixes for **TensorRT-LLM** and **Isaac Launchable**, including TensorRT-LLM deserialization flaws in MPI server and RPC testing components that could lead to RCE, data manipulation, information disclosure, or service outages. It also patched a Linux issue in Isaac Launchable involving sensitive information sent in clear text, creating risks of privilege escalation and system disruption. NVIDIA advised customers to upgrade **TensorRT-LLM** to `1.2.1` or later, and said organizations running multi-GPU deployments should use: ```bash trtllm-llmapi-launch ``` to reduce network exposure. The company has also begun publishing PSIRT bulletins on GitHub in Markdown and CSAF formats to support automated vulnerability management and faster remediation.
Jun 29, 2026
NVIDIA has disclosed multiple critical vulnerabilities in its Isaac Launchable product, each carrying a CVSS v3.1 base score of 9.8, indicating a severe risk to affected systems. The vulnerabilities include two privilege escalation flaws (CVE-2025-33223 and CVE-2025-33224) that allow attackers to execute code with unnecessary privileges, potentially leading to code execution, escalation of privileges, denial of service, information disclosure, and data tampering. Additionally, a hard-coded credential vulnerability (CVE-2025-33222) could be exploited to achieve similar impacts, including unauthorized access and manipulation of system data. All vulnerabilities are remotely exploitable and require immediate attention. NVIDIA has released security updates to address these issues and strongly recommends that users download and install the latest version of Isaac Launchable to mitigate the risks. The official security bulletin provides detailed descriptions of each CVE, their associated CWE categories, and the potential impacts. Organizations using NVIDIA Isaac Launchable should prioritize patching to prevent exploitation, as the vulnerabilities could be leveraged by remote attackers without user interaction or prior authentication.
Jun 29, 2026