Skip to content
Fencer Vulns
high 7.8

CVE-2026-47579 json

The NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode driver through which a user might trigger a use-after…

published 2026-09-30 39 d ago modified 2026-10-01 39 d ago also EUVD-2026-90126

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

The NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode driver through which a user might trigger a use-after-free condition. Successful exploitation of this issue could lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-47579 updated cvss 7.0

nvidia-driver: nvidia-driver: arbitrary code execution via use-after-free in kernel mode driver

  • Red Hat Enterprise Linux 9 libnvidia-ml, libnvidia-cfg, libnvidia-fbc, nvidia-driver, xorg-x11-nvidia, libnvidia-gpucomp, +4 more Red Hat Enterprise Linux 10 nvidia-driver
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
40 d ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • NVIDIA GeForce
  • NVIDIA RTX, Quadro, NVS
  • NVIDIA Tesla
  • NVIDIA Guest driver

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.