Vulnerability in Kernel: UAF in peak_pci_remove()
Summary
GSD-2021-1001779: can: peak_pci: peak_pci_remove(): fix UAF. Affects Kernel versions >= e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, < 447d44cd2f67a20b596ede3ca3cd67086dfd9ca9. 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 fundamental component of the Linux operating system, responsible for managing system resources and providing an interface between hardware and software. It is crucial for the proper functioning of the system. The vulnerability in question affects the Kernel's peak_pci module, which is responsible for handling CAN (Controller Area Network) devices connected via the PCI bus. The peak_pci_remove() function within this module is susceptible to a use-after-free (UAF) vulnerability.
Vulnerability Detail
The UAF vulnerability in peak_pci_remove() can be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. The vulnerability arises due to improper handling of resources during the removal of a peak_pci device. By manipulating certain parameters, an attacker can trigger the use of freed memory, leading to unpredictable behavior and potential security breaches. This vulnerability was introduced in version v3.4 of the Linux Kernel and has been fixed in version v4.9.288.
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. It is essential to apply the provided fix by updating the Linux Kernel to the recommended version.
Conclusion
The UAF vulnerability in peak_pci_remove() of the Kernel can have severe consequences, including arbitrary code execution and denial-of-service. It is crucial to update the Linux Kernel to version v4.9.288 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition on a system running the affected version of the Linux Kernel.
You can use the Vulert Playground (https://vulert.com/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.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is recommended to update the Kernel as soon as possible to prevent any potential attacks.
If updating the Kernel is not immediately feasible, it is recommended to implement other security measures such as network segmentation, access controls, and intrusion detection systems to minimize the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
