Refcount Leak in a6xx_gpu_init in Kernel
Summary
GSD-2022-1003781: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init. Affects Kernel versions >= 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a, < 6832e36f156ea35a6ed74bca72727806116effdd. 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 crucial component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The a6xx_gpu_init function in the drm/msm/a6xx module is responsible for initializing the Adreno 6xx series GPU found in Qualcomm Snapdragon SoCs. This GPU is commonly used in mobile devices and provides hardware acceleration for graphics-intensive tasks.
Vulnerability Detail
The a6xx_gpu_init function in the drm/msm/a6xx module suffers from a refcount leak vulnerability. This vulnerability allows an attacker to cause a reference count leak, leading to a use-after-free condition. By exploiting this vulnerability, an attacker could potentially execute arbitrary code with kernel privileges, compromising the integrity and security of the system. The vulnerability was introduced in version v4.19 of the Linux Kernel and was fixed in version v5.4.198.
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
No specific workaround has been provided for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the patched version.
Conclusion
The refcount leak vulnerability in a6xx_gpu_init in the Kernel can lead to a use-after-free condition and potential code execution with kernel privileges. It is crucial to update the Linux Kernel to version v5.4.198 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could allow an attacker to execute arbitrary code with kernel privileges, potentially compromising the entire system.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there are no known public exploits targeting this specific vulnerability. However, it is always recommended to apply security patches promptly to mitigate any potential risks.
No, this vulnerability requires local access to the system to exploit it. However, if an attacker gains local access, they could potentially exploit this vulnerability to escalate their privileges and gain control over the entire system.
For more details about this vulnerability, you can refer to the source information provided by the Cloud Security Alliance's GSD database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003781.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
