HID: magicmouse: fix NULL-deref on disconnect in Kernel
Summary
GSD-2021-1000775: HID: magicmouse: fix NULL-deref on disconnect. Affects Kernel versions >= 9d7b18668956c411a422d04c712994c5fdb23a4b, < b5d013c4c76b276890135b5d32803c4c63924b77. 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 critical component of the Linux operating system that manages the communication between hardware and software. It provides essential services and functions to enable the proper functioning of the system. The HID (Human Interface Device) subsystem within the Kernel handles input devices such as keyboards, mice, and touchpads. One of the supported devices is the magicmouse. However, a vulnerability has been discovered in the magicmouse driver that can lead to a NULL-dereference when disconnecting the device.
Vulnerability Detail
The vulnerability in the magicmouse driver occurs when the device is disconnected. A NULL-dereference error can occur, which may result in a system crash or other unpredictable behavior. An attacker with physical access to the affected system could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel privileges. The vulnerability was introduced in version v4.20 of the Linux Kernel and has been fixed in version v5.10.43.
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 →
Conclusion
The HID: magicmouse vulnerability in the Kernel can lead to a NULL-dereference error when disconnecting the device, potentially resulting in a system crash or other unpredictable behavior. It is crucial to update the Linux Kernel to version v5.10.43 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or other unpredictable behavior, potentially allowing an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel privileges.
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, and Vulert will analyze it for any open-source vulnerabilities, including this one.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
No, this vulnerability requires physical access to the affected system to exploit.
There are no known instances of this vulnerability being exploited in the wild at this time.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
