Memory Leak Vulnerability in drm/amd/pm Package
Summary
GSD-2021-1002700: drm/amd/pm: fix a potential gpu_metrics_table memory leak. Affects Kernel versions >= 95868b85764aff2dcbf78d3054076df75446ad15, < 222cebd995cdf11fe0d502749560f65e64990e55. 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/amd/pm package is a component of the Linux Kernel that handles power management for AMD GPUs. It provides functionality for controlling the power states and performance levels of the graphics card. The package is responsible for managing the GPU metrics table, which is used to collect and store performance data. However, a vulnerability has been discovered in the package that can lead to a memory leak in the gpu_metrics_table data structure.
Vulnerability Detail
The vulnerability in the drm/amd/pm package can result in a memory leak in the gpu_metrics_table. This can occur when the package fails to properly release memory allocated for the table, leading to a gradual depletion of system resources. An attacker could potentially exploit this vulnerability to exhaust available memory, causing system instability or denial of service. The vulnerability was introduced in version v5.10 of the Linux Kernel and has been fixed in version v5.10.88.
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 specific workaround available for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
The memory leak vulnerability in the drm/amd/pm package can have serious consequences, including system instability and denial of service. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, potentially causing system instability or denial of service due to resource exhaustion.
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 analyze the dependencies and alert you if any vulnerabilities are found.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to prevent any potential exploitation.
No, the recommended solution is to update the Linux Kernel to the fixed version. This ensures that the necessary patch is applied to address the memory leak vulnerability.
You can find more information about the vulnerability in the Linux Kernel repository. The specific commit that fixes the vulnerability is 222cebd995cdf11fe0d502749560f65e64990e55.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.