Memory Leak Vulnerability in drm/nouveau/kms/nv50-
Summary
GSD-2021-1001625: drm/nouveau/kms/nv50-: fix file release memory leak. Affects Kernel versions >= 12885ecbfe62df4358d452080d3b8feef54ec8cb, < 65fff0a8efcdca8d84ffe3e23057c3b32403482d. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The drm/nouveau/kms/nv50- package is a component of the Linux Kernel. It is responsible for managing the display and graphics capabilities of NVIDIA GPUs using the Nouveau driver. This package provides kernel mode-setting (KMS) support for the nv50- family of GPUs. The vulnerability in this package leads to a memory leak when releasing files, which can result in resource exhaustion and potential denial-of-service attacks.
Vulnerability Detail
The memory leak vulnerability in drm/nouveau/kms/nv50- occurs when releasing files. This can be exploited by an attacker to exhaust system resources, leading to a denial-of-service condition. The vulnerability was introduced in Linux Kernel version v5.9 by commit 12885ecbfe62df4358d452080d3b8feef54ec8cb and is fixed in version v5.10.73 by commit 65fff0a8efcdca8d84ffe3e23057c3b32403482d. It is important to note that the impact and attack plausibility of this vulnerability have not been proven.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Conclusion
The memory leak vulnerability in drm/nouveau/kms/nv50- can lead to resource exhaustion and potential denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.10.73 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, causing resource exhaustion and potential denial-of-service attacks.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
There are no known exploits for this vulnerability at this time. However, it is still important to apply the fix to prevent potential exploitation.
This vulnerability was discovered by the security research team at Vulert, a platform that monitors and alerts for open-source vulnerabilities in software.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
