Vulnerability in Kernel: ASoC mxs-saif
Summary
GSD-2022-1003098: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe. Affects Kernel versions >= 08641c7c74dddfcd726512edfaa3b4cbe42e523e, < 4e2a1bcc51bdebed48176f6e88c150f175983f9c. 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 critical component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. ASoC (Audio System on Chip) is a subsystem within the Kernel that provides support for audio devices. The mxs-saif driver is part of the ASoC framework and is used for audio input and output on MXS-based systems. This vulnerability, identified as GSD-2022-1003098, affects the mxs-saif driver and can lead to a refcount leak in the mxs_saif_probe function.
Vulnerability Detail
The mxs_saif_probe function in the mxs-saif driver of the ASoC subsystem in the Kernel suffers from a refcount leak. This vulnerability was introduced in version v3.5 of the Kernel by commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and was fixed in version v5.17.14 by commit 4e2a1bcc51bdebed48176f6e88c150f175983f9c. The refcount leak occurs during the probe function, which is responsible for initializing the mxs-saif driver. If this vulnerability is exploited, it could result in a resource leak, potentially leading to system instability or denial of service.
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 known workaround for this vulnerability. It is crucial to update the Kernel to the fixed version as soon as possible.
Conclusion
The vulnerability in the mxs-saif driver of the ASoC subsystem in the Kernel can lead to a refcount leak, potentially resulting in system instability or denial of service. It is crucial to update the Kernel to version v5.17.14 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
If this vulnerability is exploited, it could result in a resource leak, potentially leading to system instability 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 package-lock.json file and Vulert will analyze it in real-time.
At the time of this report, there are no known exploits for this vulnerability. However, it is still important to update the Kernel to the fixed version to mitigate any potential risks.
This vulnerability requires local access to the system in order to exploit it. Remote exploitation is not possible.
For more details about this vulnerability, you can refer to the vulnerability database entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003098.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
