CVE Vulnerabilities

CVE-2022-28187

Missing Release of Resource after Effective Lifetime

Published: May 17, 2022 | Modified: May 26, 2022
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4.9 MEDIUM
AV:L/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where the memory management software does not release a resource after its effective lifetime has ended, which may lead to denial of service.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Gpu_display_driver Nvidia - (including) - (including)
Nvidia-graphics-drivers-304 Ubuntu esm-infra/xenial *
Nvidia-graphics-drivers-304 Ubuntu trusty *
Nvidia-graphics-drivers-304 Ubuntu xenial *
Nvidia-graphics-drivers-304-updates Ubuntu trusty *
Nvidia-graphics-drivers-304-updates Ubuntu xenial *
Nvidia-graphics-drivers-340 Ubuntu bionic *
Nvidia-graphics-drivers-340 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-340 Ubuntu esm-infra/xenial *
Nvidia-graphics-drivers-340 Ubuntu focal *
Nvidia-graphics-drivers-340 Ubuntu trusty *
Nvidia-graphics-drivers-340 Ubuntu xenial *
Nvidia-graphics-drivers-340-updates Ubuntu trusty *
Nvidia-graphics-drivers-352 Ubuntu trusty *
Nvidia-graphics-drivers-352-updates Ubuntu trusty *
Nvidia-graphics-drivers-367 Ubuntu trusty *
Nvidia-graphics-drivers-375 Ubuntu trusty *
Nvidia-graphics-drivers-384 Ubuntu trusty *
Nvidia-graphics-drivers-384 Ubuntu xenial *
Nvidia-graphics-drivers-430 Ubuntu bionic *
Nvidia-graphics-drivers-430 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-430 Ubuntu focal *
Nvidia-graphics-drivers-430 Ubuntu impish *
Nvidia-graphics-drivers-430 Ubuntu jammy *
Nvidia-graphics-drivers-430 Ubuntu kinetic *
Nvidia-graphics-drivers-430 Ubuntu lunar *
Nvidia-graphics-drivers-430 Ubuntu mantic *
Nvidia-graphics-drivers-435 Ubuntu bionic *
Nvidia-graphics-drivers-435 Ubuntu esm-apps/jammy *
Nvidia-graphics-drivers-435 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-435 Ubuntu focal *
Nvidia-graphics-drivers-435 Ubuntu impish *
Nvidia-graphics-drivers-435 Ubuntu jammy *
Nvidia-graphics-drivers-435 Ubuntu kinetic *
Nvidia-graphics-drivers-435 Ubuntu lunar *
Nvidia-graphics-drivers-435 Ubuntu mantic *
Nvidia-graphics-drivers-440 Ubuntu bionic *
Nvidia-graphics-drivers-440 Ubuntu esm-infra/bionic *
Nvidia-graphics-drivers-440 Ubuntu focal *
Nvidia-graphics-drivers-440 Ubuntu impish *
Nvidia-graphics-drivers-440 Ubuntu jammy *
Nvidia-graphics-drivers-440 Ubuntu kinetic *
Nvidia-graphics-drivers-440 Ubuntu lunar *
Nvidia-graphics-drivers-440 Ubuntu mantic *
Nvidia-graphics-drivers-440-server Ubuntu bionic *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/bionic *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/focal *
Nvidia-graphics-drivers-440-server Ubuntu esm-apps/jammy *
Nvidia-graphics-drivers-440-server Ubuntu focal *
Nvidia-graphics-drivers-440-server Ubuntu impish *
Nvidia-graphics-drivers-440-server Ubuntu jammy *
Nvidia-graphics-drivers-440-server Ubuntu kinetic *
Nvidia-graphics-drivers-440-server Ubuntu lunar *
Nvidia-graphics-drivers-455 Ubuntu bionic *
Nvidia-graphics-drivers-455 Ubuntu esm-apps/bionic *
Nvidia-graphics-drivers-455 Ubuntu esm-apps/focal *
Nvidia-graphics-drivers-455 Ubuntu focal *
Nvidia-graphics-drivers-455 Ubuntu impish *
Nvidia-graphics-drivers-455 Ubuntu jammy *
Nvidia-graphics-drivers-455 Ubuntu kinetic *
Nvidia-graphics-drivers-455 Ubuntu lunar *
Nvidia-graphics-drivers-455 Ubuntu mantic *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References