Vulnerability in drm/ttm: Fix Memory Leak in ttm_transfered_destroy
Summary
UVI-2021-1002062: drm/ttm: fix memleak in ttm_transfered_destroy. Affects Kernel versions < c21b4002214c1c7e7b627b9b53375612f7aab6db. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The drm/ttm package is a component of the Linux Kernel that provides support for graphics memory management. It is responsible for managing the transfer of data between the graphics driver and the graphics memory. The ttm_transfered_destroy function within the package is vulnerable to a memory leak issue.
Vulnerability Detail
The vulnerability in ttm_transfered_destroy function can lead to a memory leak. When this function is called, it fails to release allocated memory, resulting in a gradual accumulation of memory over time. This can potentially exhaust system resources and lead to performance degradation or even system crashes. Attackers may be able to exploit this vulnerability to launch denial-of-service attacks or gain unauthorized access to sensitive information.
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 →
Workaround
There is no known workaround for this vulnerability. It is essential to update the Linux Kernel to the recommended version to mitigate the risk of memory leaks.
Conclusion
The vulnerability in drm/ttm's ttm_transfered_destroy function can lead to memory leaks, potentially causing performance degradation or system crashes. It is crucial to update the Linux Kernel to version v5.10.77 or later to fix this vulnerability. No known workarounds exist, and attempting manual fixes without proper expertise is not recommended. For further support, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a memory leak, leading to performance degradation, system crashes, or potential unauthorized access to sensitive information.
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 to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to update the Linux Kernel to the recommended version to prevent potential exploitation.
No, updating the Linux Kernel to the recommended version is the only known solution to fix this vulnerability. It is not recommended to attempt manual fixes without the proper expertise and knowledge.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
