Refcount Leak in a6xx_gpu_init in Kernel
Summary
GSD-2022-1003376: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init. Affects Kernel versions >= 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a, < edff4c1af831d0c02e654eed9da7d74174de49d5. 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 that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for device drivers, memory management, and process scheduling. The a6xx_gpu_init function in the drm/msm/a6xx module is responsible for initializing the Adreno 6xx series GPU found in certain Qualcomm Snapdragon SoCs. This module is utilized by the graphics driver to enable and control the GPU's operations.
Vulnerability Detail
The a6xx_gpu_init function in the drm/msm/a6xx module suffers from a refcount leak vulnerability. This vulnerability, identified as GSD-2022-1003376, was introduced in version v4.19 of the Linux Kernel by commit 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a. It was fixed in version v5.15.46 by commit edff4c1af831d0c02e654eed9da7d74174de49d5. The vulnerability occurs when the refcount of the GPU is not properly decremented, leading to a resource leak. Although the impact and attack plausibility have not been proven, this vulnerability has the potential to be exploited by malicious actors to exhaust system resources and potentially cause a denial-of-service condition.
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 this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is advised to update to the patched version as soon as possible.
Conclusion
The refcount leak vulnerability in the a6xx_gpu_init function of the Kernel's drm/msm/a6xx module has the potential to be exploited by malicious actors to exhaust system resources and cause a denial-of-service condition. It is crucial to update the Linux Kernel to version v5.15.46 or later to mitigate this vulnerability. If you have any further questions or need assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to be exploited by malicious actors to exhaust system resources and potentially cause a denial-of-service condition.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it in real-time.
The remote exploitability of this vulnerability has not been determined. However, it is always recommended to apply security patches and updates to mitigate potential risks.
There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the fix to ensure the security and stability of your system.
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.
