Use After Free Vulnerability in pch_can
Summary
GSD-2021-1002453: can: pch_can: pch_can_rx_normal: fix use after free. Affects Kernel versions >= b21d18b51b31a24d17f883b678432fbdee3d5675, < abb4eff3dcd2e583060082a18a8dbf31f02689d4. 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 pch_can package is a part of the Linux Kernel ecosystem and is responsible for handling CAN (Controller Area Network) communication. CAN is a widely used protocol for communication between microcontrollers and devices in automotive and industrial applications. The pch_can package provides support for the PCH (Platform Controller Hub) CAN controller found in Intel chipsets. This vulnerability affects the pch_can_rx_normal function in the pch_can module.
Vulnerability Detail
The use after free vulnerability in pch_can_rx_normal function allows an attacker to exploit a freed memory region. By manipulating certain CAN messages, an attacker can trigger the use of this freed memory, leading to a potential crash or arbitrary code execution. The vulnerability was introduced in version v2.6.37 of the Linux Kernel and has been fixed in version v5.4.165.
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 mentioned above.
Conclusion
The use after free vulnerability in pch_can_rx_normal function can potentially lead to crashes or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.4.165 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a crash or arbitrary code execution, depending on how it is exploited.
Yes, this vulnerability can be exploited remotely if the affected system is connected to a network.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
No, a CVSS score has not been assigned to this vulnerability at the time of this report.
For more information about this vulnerability, you can refer to the source link provided in the database_specific section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.