Refcount Leak in a6xx_gpu_init in Kernel
Summary
GSD-2022-1003087: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init. Affects Kernel versions >= 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a, < 65ddbc0d26824e2a5d6154d01d8cf39344900213. 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 manages core system functions, such as memory management, process scheduling, and device drivers. It provides an interface between the hardware and software layers of the system. The a6xx_gpu_init function is part of the drm/msm/a6xx module, which handles graphics processing for Qualcomm Adreno GPUs. This vulnerability in a6xx_gpu_init can lead to a refcount leak, potentially causing memory leaks and resource exhaustion.
Vulnerability Detail
The vulnerability in a6xx_gpu_init arises from a refcount leak. When initializing the a6xx GPU, the function fails to properly release resources in certain error paths, leading to a refcount leak. This can result in memory leaks and resource exhaustion, potentially impacting system stability and performance. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or execute arbitrary code with elevated privileges.
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 provided for this vulnerability. However, applying the recommended fix by updating the Linux Kernel to the latest version will address the issue.
Conclusion
The refcount leak vulnerability in a6xx_gpu_init in the Kernel can lead to memory leaks, resource exhaustion, and potential code execution with elevated privileges. It is crucial to update the Linux Kernel to version v5.17.14 or later to fix this vulnerability. Applying the recommended fix will ensure proper resource release and prevent refcount leaks. For additional support, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory leaks and resource exhaustion, potentially impacting system stability and performance. It may also allow an attacker to execute arbitrary code with elevated privileges.
You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
This vulnerability can potentially be exploited remotely if an attacker can gain access to the affected system. It is crucial to update the Linux Kernel to the latest version to prevent any remote exploitation.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
