← console
voxell vciy

CVE-2021-1116

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: gpu display driver 392.68; gpu display driver 463.15; gpu display driver 472.39; gpu display driver 496.49 upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where a NULL pointer dereference in the kernel, created within user mode code, may lead to a denial of service in the form of a system crash.

weakness
CWE-476: NULL Pointer Dereference
affected
NVIDIA GPU Display Driver
published ranges
nvidia gpu display driver >= 390 < 392.68; nvidia gpu display driver >= 460 < 463.15; nvidia gpu display driver >= 470 < 472.39; nvidia gpu display driver >= 490 < 496.49
first unaffected version, by branch
gpu display driver 392.68; gpu display driver 463.15; gpu display driver 472.39; gpu display driver 496.49
severity
5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
assigned by
nvidia
published
2021-10-27

check us nvidia.custhelp.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
28 Oct 20210.00518
6 Jan 20220.02283
4 Feb 20220.01404
1 Apr 20220.00885
7 Mar 20230.00043scoring model v2023.03.01
8 Mar 20230.00043
20 May 20230.00044
17 Mar 20250.00045scoring model v2025.03.14
29 Mar 20250.00047
30 Mar 20250.00045
15 Jun 20260.00212scoring model v2026.06.15
20 Aug 20260.00219

12 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-08-20 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: gpu display driver 392.68; gpu display driver 463.15; gpu display driver 472.39; gpu display driver 496.49. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-1116', '2026-11-02T23:59:59.999999Z', now());