Use After Free Vulnerability in can: sja1000
Summary
GSD-2021-1002362: can: sja1000: fix use after free in ems_pcmcia_add_card(). Affects Kernel versions >= fd734c6f25aea4b2b44b045e489aec67b388577e, < cbd86110546f7f730a1f5d7de56c944a336c15c4. 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 can: sja1000 package is a component of the Linux Kernel, which is responsible for handling CAN (Controller Area Network) communication. CAN is a serial communication protocol used in automotive and industrial applications. The sja1000 driver provides support for the SJA1000 CAN controller chip. This vulnerability affects the functionality of the sja1000 driver and can potentially lead to security breaches.
Vulnerability Detail
The use after free vulnerability in the ems_pcmcia_add_card() function of the can: sja1000 package allows an attacker to exploit a freed memory region. This can result in a variety of consequences, including remote code execution, denial of service, or information disclosure. The vulnerability was introduced in version v3.2 of the Linux Kernel and has been fixed in version v4.4.295.
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 available for this vulnerability. However, as a general security practice, it is recommended to implement other layers of security, such as network segmentation, access controls, and intrusion detection systems, to mitigate the risk of exploitation.
Conclusion
The use after free vulnerability in the can: sja1000 package of the Linux Kernel can have serious security implications. It is crucial to update the Linux Kernel to version v4.4.295 or later to fix this vulnerability. Additionally, implementing other security measures can help mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific exploitation scenario. It can potentially lead to remote code execution, denial of service, or information disclosure.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch for this vulnerability has been released in version v4.4.295 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.
Yes, this vulnerability can be exploited remotely if an attacker can send malicious CAN messages to the affected system.
There are no known instances of this vulnerability being exploited in the wild at the time of this report. However, it is important to apply the necessary security updates to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
