USB: max-3421: Prevent Corruption of Freed Memory in Linux Kernel
Summary
GSD-2021-1001306: usb: max-3421: Prevent corruption of freed memory. Affects Kernel versions >= 2d53139f31626bad6f8983d8e519ddde2cbba921, < 863d071dbcd54dacf47192a1365faec46b7a68ca. 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 Linux Kernel is a widely used open-source monolithic Unix-like computer operating system kernel. It provides essential services for the functioning of the operating system, including managing the system's resources and facilitating communication between hardware and software components. The USB subsystem in the Linux Kernel allows for the connection and communication with USB devices. The 'max-3421' driver is responsible for supporting the Maxim MAX3421 USB peripheral controller. This vulnerability affects the 'max-3421' driver in the Linux Kernel.
Vulnerability Detail
The vulnerability in the 'max-3421' driver of the Linux Kernel allows for the corruption of freed memory. When certain operations are performed on USB devices using the 'max-3421' driver, memory that has been previously freed may be accessed, leading to potential memory corruption. This vulnerability could be exploited by an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. It was introduced in version v3.16 of the Linux Kernel and has been fixed in version v5.4.136.
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 provided for this vulnerability.
Conclusion
The 'max-3421' driver in the Linux Kernel is vulnerable to a memory corruption issue that could be exploited by an attacker. It is crucial to update the Linux Kernel to version v5.4.136 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 could allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service condition.
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 analyze the dependencies and alert you if any open-source vulnerabilities, including this one, are found.
Yes, a patch for this vulnerability has been included in Linux Kernel version v5.4.136. It is recommended to update to this version or a later one to fix the vulnerability.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to malicious USB devices or if the attacker has network access to the system.
There are no known instances of this vulnerability being exploited in the wild at this time.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
