Vulnerability in imx-hdmi Package: Refcount Leak in imx_hdmi_probe
Summary
GSD-2022-1003105: ASoC: imx-hdmi: Fix refcount leak in imx_hdmi_probe. Affects Kernel versions >= 6a5f850aa83a1d844d27e3e53ca2f247e55d438b, < 8205a0114db10ec41bd2b748cdd7528632082eca. 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 imx-hdmi package is a component of the ASoC (Audio System on Chip) framework in the Linux Kernel. It provides support for HDMI audio on i.MX platforms. The imx_hdmi_probe function is responsible for initializing the HDMI audio driver. However, a refcount leak has been identified in this function, which can lead to resource exhaustion and potential system instability.
Vulnerability Detail
The vulnerability arises from a refcount leak in the imx_hdmi_probe function of the imx-hdmi package. When the function is called, it fails to properly release a reference count on a resource, resulting in a leak. This can lead to resource exhaustion over time, potentially causing system instability or denial of service. The vulnerability was introduced in version v5.11 of the Linux Kernel and has been fixed in version v5.17.14.
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 workaround has been provided for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.
Conclusion
The imx-hdmi package in the Linux Kernel is vulnerable to a refcount leak in the imx_hdmi_probe function. This vulnerability can lead to resource exhaustion and potential system instability. To mitigate this issue, it is recommended to update the Linux Kernel to version v5.17.14 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential system instability. It may also be possible for an attacker to exploit this vulnerability to cause a denial of service.
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 to the playground and it will alert you in real-time if any open-source vulnerabilities, including this one, are detected.
At the time of this report, no known exploits for this vulnerability have been disclosed. However, it is always recommended to apply security patches promptly to mitigate potential risks.
No, the recommended mitigation for this vulnerability is to update the Linux Kernel to version v5.17.14 or later.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1003105 at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003105.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.