CyberSecBulletin
CVE-2026-47602NVD status: Awaiting Analysis

GeForce: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2026-47602 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in GeForce from NVIDIA, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected GeForce versions: All driver versions prior to 610.60; All driver versions prior to 616.56; All driver versions prior to 615.71.09, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.11% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of GeForce you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
NVIDIAGeForceAll driver versions prior to 610.60; All driver versions prior to 616.56; All driver versions prior to 615.71.09; All driver versions prior to 610.57.04; All driver versions prior to 595.91.07; All driver versions prior to 580.178.04Not stated
NVIDIARTX, Quadro, NVSAll driver versions prior to 610.88; All driver versions prior to 616.92; All driver versions prior to 582.78; All driver versions prior to 596.86; All driver versions prior to 615.71.09; All driver versions prior to 610.57.04; All driver versions prior to 595.91.07; All driver versions prior to 580.178.04Not stated
NVIDIATeslaAll driver versions prior to 596.86; All driver versions prior to 616.92; All driver versions prior to 610.88; All driver versions prior to 615.71.09; All driver versions prior to 610.57.04; All driver versions prior to 595.91.07; All driver versions prior to 580.178.04Not stated
NVIDIAVirtual GPU Manager595.71.03(All versions prior to and including vGPU 20.1); 580.159.01(All versions prior to and including vGPU 19.5); 596.38(All versions prior to and including vGPU 20.1); 582.51(All versions prior to and including vGPU 19.5)Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by CNA (nvidia.com).

Official description

NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode driver where a local user can cause the driver to dereference an untrusted pointer. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).

References

Other vulnerabilities in GeForce

All GeForce vulnerabilities

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.