Vulnerability in drm/amd/display Package: Free Local Data After Use
Summary
GSD-2021-1000270: drm/amd/display: Free local data after use. Affects Kernel versions >= 3a00c04212d1cfe1426338b78f4ead623508c874, < 296443139f893b554dddd56a99ba8471ab5802d4. 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/display package is a component of the Linux Kernel, which is responsible for managing display functionality on AMD graphics cards. It provides the necessary drivers and interfaces for rendering graphics and handling display output. The package is widely used in Linux-based systems that utilize AMD GPUs. However, a vulnerability has been discovered in this package that could potentially lead to security breaches and data corruption.
Vulnerability Detail
The vulnerability in the drm/amd/display package involves the improper handling of local data, which is not properly freed after use. This can result in memory leaks and potential exploitation by malicious actors. If successfully exploited, an attacker could gain unauthorized access to sensitive information, execute arbitrary code, or cause system crashes. The vulnerability was introduced in version v5.12 of the Linux Kernel and has been fixed in version v5.12.4.
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
As a temporary workaround, users can disable the affected functionality by modifying the kernel configuration or disabling the corresponding kernel module. However, this may result in the loss of certain display features or reduced performance. It is strongly recommended to apply the official fix as soon as possible.
Conclusion
The vulnerability in the drm/amd/display package of the Linux Kernel can potentially lead to security breaches and data corruption. It is crucial to update the kernel to version v5.12.4 or later to mitigate this vulnerability. Users can also utilize the Vulert Playground (https://vulert.com/scanner) to check if their system is affected and seek further assistance from DevNack.com for vulnerability remediation.
See every vulnerability recorded for Kernel →
FAQ
If exploited, this vulnerability could allow attackers to gain unauthorized access to sensitive information, execute arbitrary code, or cause system crashes.
You can use the Vulert Playground (https://vulert.com/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 known vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
As a temporary workaround, you can disable the affected functionality by modifying the kernel configuration or disabling the corresponding kernel module. However, it is strongly recommended to apply the official fix as soon as possible.
You can find more information about the fix in the Linux Kernel repository. The commit that addresses this vulnerability is 296443139f893b554dddd56a99ba8471ab5802d4.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
