Double Free Vulnerability in remoteproc: mtk_scp
Summary
GSD-2022-1002650: remoteproc: mtk_scp: Fix a potential double free. Affects Kernel versions >= c1407ac1099ab9726c31d38d806f3150f494c494, < adc02700236613b344a947a897fc2741d52a43b9. 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 remoteproc is a subsystem in the Linux Kernel that allows for the management of remote processors. It provides an interface for loading firmware and controlling the execution of code on these processors. The mtk_scp driver is a specific driver within remoteproc that is used for MediaTek System Control Processors (SCP). These SCPs are responsible for various tasks such as power management and device control. The vulnerability in question is a potential double free issue within the mtk_scp driver.
Vulnerability Detail
The double free vulnerability occurs when a program attempts to free the same memory address twice. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a denial of service. In the case of the mtk_scp driver, the vulnerability arises from a potential double free situation. The impact and attack plausibility of this vulnerability have not been proven yet. However, it is important to address this issue to prevent any potential exploitation.
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 mentioned for this vulnerability.
Conclusion
The double free vulnerability in the mtk_scp driver of the remoteproc subsystem in the Linux Kernel can potentially lead to memory corruption and allow for arbitrary code execution or denial of service. It is crucial to update to the latest version of the Linux Kernel (v5.18.4 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. However, if exploited, it could potentially allow an attacker to execute arbitrary code or 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 and Vulert will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the moment. However, it is important to update to the latest version of the Linux Kernel to mitigate any potential risks.
The specific prerequisites for exploiting this vulnerability have not been disclosed. However, keeping your system up to date with the latest security patches is always recommended to minimize the risk of 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.
