Use After Free Vulnerability in m_can_tx_handler() Function in Kernel
Summary
GSD-2022-1002137: can: m_can: m_can_tx_handler(): fix use after free of skb. Affects Kernel versions >= 80646733f11c2e9de3b6339f7e635047e6087280, < 869016a2938ac44f7b2fb7fc22c89edad99eb9b3. 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 the system's resources and facilitates communication between hardware and software. It provides essential functions and services for the proper functioning of the system. The m_can_tx_handler() function is responsible for handling transmission requests in the Controller Area Network (CAN) subsystem of the Kernel. CAN is a widely used network protocol for communication between microcontrollers and devices in automotive and industrial applications.
Vulnerability Detail
The m_can_tx_handler() function in the Kernel suffers from a use after free vulnerability. This vulnerability occurs when the function continues to reference a memory object (skb) after it has been freed. An attacker could exploit this vulnerability by manipulating the freed memory object, potentially leading to a variety of security issues such as privilege escalation, information disclosure, or denial of service. The vulnerability was introduced in version v3.18 of the Kernel and is fixed in version v5.10.110.
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 recommended to apply the fix provided by updating the Kernel to the latest version.
Conclusion
The use after free vulnerability in the m_can_tx_handler() function of the Kernel can have serious security implications. It is crucial to update the Kernel to version v5.10.110 or later to mitigate the risk associated with this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially be exploited by an attacker to gain elevated privileges, access sensitive information, or disrupt the normal operation of the system.
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 analyze the dependencies and alert you if any vulnerabilities, including this one, are found.
There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the fix as soon as possible to mitigate the risk.
It is highly recommended to update the Kernel to the latest version to apply the necessary fix. Manual patching may be complex and error-prone, and it is best to rely on official updates provided by the Kernel maintainers.
You can find more information about this vulnerability in the GSD-2022-1002137 entry of the GSD Database maintained by the Cloud Security Alliance. The entry provides details about the vulnerability, its impact, and the fix provided by the Linux Kernel developers.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
