7.8

CVE-2025-33217

Medienbericht
NVIDIA Display Driver for Windows contains a vulnerability where an attacker could trigger a use after free. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, denial of service, and information disclosure.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerNVIDIA
≫
Produkt GeForce
Default Statusunaffected
Version All driver versions prior to 591.59
Status affected
HerstellerNVIDIA
≫
Produkt RTX PRO, RTX, Quadro
Default Statusunaffected
Version All driver versions prior to 591.59
Status affected
HerstellerNVIDIA
≫
Produkt RTX PRO, RTX, Quadro
Default Statusunaffected
Version All driver versions prior to 582.16
Status affected
HerstellerNVIDIA
≫
Produkt RTX PRO, RTX, Quadro
Default Statusunaffected
Version All driver versions prior to 573.96
Status affected
HerstellerNVIDIA
≫
Produkt RTX PRO, RTX, Quadro
Default Statusunaffected
Version All driver versions prior to 539.64
Status affected
HerstellerNVIDIA
≫
Produkt Tesla
Default Statusunaffected
Version All driver versions prior to 591.59
Status affected
HerstellerNVIDIA
≫
Produkt Tesla
Default Statusunaffected
Version All driver versions prior to 582.16
Status affected
HerstellerNVIDIA
≫
Produkt Tesla
Default Statusunaffected
Version All driver versions prior to 573.96
Status affected
HerstellerNVIDIA
≫
Produkt Tesla
Default Statusunaffected
Version All driver versions prior to 539.64
Status affected
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.01% 0.003
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
psirt@nvidia.com 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.