NVIDIA GPU Display Driver: Out-of-bounds Write
CVE-2022-28181 is a critical-severity out-of-bounds write vulnerability in NVIDIA GPU Display Driver from NVIDIA, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected NVIDIA GPU Display Driver versions: All GPU Driver versions for Windows and Linux. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.13% chance of exploitation within 30 days, higher than 67% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Virtual GPU to 11.8 or 13.3, whichever matches your release line, or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | NVIDIA GPU Display Driver | All GPU Driver versions for Windows and Linux | Not stated |
| NVIDIA | Virtual GPU | 11.0 up to, but not including, 11.8; 13.0 up to, but not including, 13.3; 14.0 | 11.8, 13.3 |
| NVIDIA | GPU Display Driver | Not specified in the record | 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
- NetworkCan be exploited remotely over a network, including the internet.
- 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
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.5 | High | CNA (nvidia.com) |
| CVSS 3.1 | 9.9 | Critical | NVD |
| CVSS 2.0 | 6.9 | Medium | NVD |
Official description
NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where an unprivileged regular user on the network can cause an out-of-bounds write through a specially crafted shader, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The scope of the impact may extend to other components.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
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.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- security.gentoo.org/glsa/202310-02Third Party Advisory
Other vulnerabilities in NVIDIA GPU Display Driver
- 7.8 High severity
- 7.1 High severity
- 7.8 High severity
- 7.1 High severity
Recent Out-of-bounds Write vulnerabilities
- 9.3 High severity
- 9.3 High severity
- 9.3 High severity
- 7.8 High severity
- 9.3 High severity
- 9.3 High severity
Spotted an error? Tell us.