Use after free vulnerability in net: qrtr: MHI send
Summary
GSD-2021-1000163: net: qrtr: Avoid potential use after free in MHI send. Affects Kernel versions >= 6e728f321393b1fce9e1c2c3e55f9f7c15991321, < 48ec949ac979b4b42d740f67b6177797af834f80. 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 affected package is the Linux Kernel, which is a critical component of the Linux operating system. It provides the core functionality and interfaces for the system. The net: qrtr module is responsible for handling communication between different subsystems in the kernel. The MHI (Modem Host Interface) send function is used to send data over the QRTR (Qualcomm Radio Transport) protocol. This vulnerability specifically affects the MHI send function in the qrtr module.
Vulnerability Detail
The vulnerability is a potential use after free issue in the MHI send function of the qrtr module. A use after free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed. In this case, there is a possibility of accessing freed memory in the MHI send function, which can lead to various security issues such as crashes, privilege escalation, or arbitrary code execution. The vulnerability was introduced in version v5.8 of the Linux Kernel and is fixed in version v5.10.35.
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. The recommended approach is to update the Linux Kernel to the fixed version.
Conclusion
In conclusion, the net: qrtr module in the Linux Kernel is vulnerable to a use after free issue in the MHI send function. This vulnerability can have various security implications and should be addressed by updating the Linux Kernel to version v5.10.35 or later. It is recommended to regularly apply security updates and follow best practices for system maintenance. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific system and usage scenario. It can potentially lead to crashes, privilege escalation, or arbitrary code execution, which can be exploited by attackers to gain unauthorized access or disrupt the system.
You can check if your system is affected by this vulnerability by verifying the version of the Linux Kernel installed. If the version is earlier than v5.10.35, it is recommended to update to the fixed version.
At the time of this report, there are no known public exploits for this vulnerability. However, it is always recommended to apply security updates promptly to mitigate the risk of potential exploitation.
The specific conditions for remote exploitation of this vulnerability are not mentioned in the available information. However, it is important to keep the system up to date with security patches to minimize the risk of remote exploitation.
You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the associated commit history. Additionally, you can refer to the provided references link for further details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
