usb: max-3421: Prevent corruption of freed memory in Kernel
Summary
GSD-2021-1001466: usb: max-3421: Prevent corruption of freed memory. Affects Kernel versions >= 2d53139f31626bad6f8983d8e519ddde2cbba921, < fc2a7c2280fa2be8ff9b5af702368fcd49a0acdb. 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 acts as a bridge between the hardware and software layers. It provides essential functionalities, such as device drivers, memory management, and process scheduling. The USB subsystem in the Kernel enables communication with USB devices. However, a vulnerability has been discovered in the max-3421 driver, which can lead to the corruption of freed memory.
Vulnerability Detail
The vulnerability in the max-3421 driver of the Kernel allows for the corruption of freed memory. When certain operations are performed on USB devices, memory that has been freed may still be accessed, leading to potential memory corruption. This can result in various security issues, including crashes, privilege escalation, and arbitrary code execution. The vulnerability was introduced in version v3.16 of the Kernel and has been fixed in version v4.4.277.
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. It is advised to apply the fix by updating the Kernel to the recommended version.
Conclusion
The usb: max-3421 vulnerability in the Kernel can lead to memory corruption and potential security risks. It is crucial to update the Kernel to version v4.4.277 or later to mitigate these risks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption, which may result in crashes, privilege escalation, and arbitrary code execution.
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 to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if an attacker can send malicious USB requests to the affected system.
The recommended solution is to update the Kernel to the fixed version. However, if updating is not feasible, additional security measures such as restricting USB device access or implementing intrusion detection systems can help mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
