HID: usbhid: Free raw_report buffers in usbhid_stop
Summary
GSD-2021-1001637: HID: usbhid: free raw_report buffers in usbhid_stop. Affects Kernel versions < f7ac4d24e1610b92689946fa88177673f1e88a3f. 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 that provides core functionalities and interfaces with hardware devices. The usbhid module is responsible for handling USB Human Interface Devices (HID), such as keyboards and mice. It allows communication between the USB HID devices and the operating system, enabling users to interact with their computers. However, a vulnerability has been discovered in the usbhid module that could potentially lead to security issues.
Vulnerability Detail
The HID: usbhid vulnerability arises from a failure to properly free raw_report buffers in the usbhid_stop function. This vulnerability could be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. By sending specially crafted input to a vulnerable system, an attacker may be able to trigger a buffer overflow or use-after-free vulnerability, leading to the execution of malicious code or system crashes. This could result in unauthorized access, data leakage, or system instability.
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 essential to apply the official fix by updating the Kernel to a version that includes the necessary patch.
Conclusion
The HID: usbhid vulnerability in the Linux Kernel's usbhid module could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition. It is crucial to update the Kernel to a version that includes the fix for this vulnerability to mitigate any potential risks. Regularly updating the Kernel is recommended to ensure the latest security patches are applied. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition. This could lead to unauthorized access, data leakage, or system instability.
You can use the Vulert Playground at Vulert 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 vulnerabilities are found.
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.
The only effective mitigation is to update the Kernel to a version that includes the fix for this vulnerability. Regularly updating the Kernel is essential to ensure the latest security patches are applied.
You can find more information about this vulnerability in the official Linux Kernel security advisory or by referring to the provided references link in the vulnerability details section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.