Use-after-free read vulnerability in drm_getunique() in Kernel
Summary
GSD-2021-1001019: drm: Fix use-after-free read in drm_getunique(). Affects Kernel versions < f773f8cccac13c7e7bbd9182e7996c727742488e. 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 Kernel is a fundamental component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It manages system resources, including memory, processes, and device drivers. The drm_getunique() function is part of the Direct Rendering Manager (DRM) subsystem in the Kernel, which handles graphics rendering and display operations. This vulnerability affects the Kernel version prior to v5.12.11.
Vulnerability Detail
The vulnerability in drm_getunique() is a use-after-free read issue. A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed, leading to potential memory corruption and arbitrary code execution. In this case, the vulnerability allows an attacker to read from freed memory, potentially leaking sensitive information or causing a denial-of-service condition. 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 →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The use-after-free read vulnerability in drm_getunique() in the Kernel can potentially lead to memory corruption or information leakage. It is recommended to update the Kernel to version v5.12.11 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to memory corruption, information leakage, or denial-of-service.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability has been fixed in Linux Kernel version v5.12.11. Users are advised to update their Kernel to the latest version to apply the patch.
There are no known exploits for this vulnerability at the moment.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2021-1001019.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
