HID: bigben: fix slab-out-of-bounds Write in bigben_probe
Summary
GSD-2022-1003605: HID: bigben: fix slab-out-of-bounds Write in bigben_probe. Affects Kernel versions < 296f8ca0f73f5268cd9b85cf72ff783596b2264e. 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 HID (Human Interface Device) bigben is a component of the Linux Kernel. It is responsible for handling input devices such as keyboards, mice, and game controllers. The bigben_probe function is a part of the bigben driver, which is used to initialize and manage the bigben device. This vulnerability, identified as GSD-2022-1003605, is a slab-out-of-bounds write issue in the bigben_probe function.
Vulnerability Detail
The slab-out-of-bounds write vulnerability in the bigben_probe function allows an attacker to write data beyond the bounds of an allocated slab. This can lead to memory corruption, which may result in system crashes, privilege escalation, or the execution of arbitrary code. The vulnerability has been fixed in Linux Kernel version v5.10.121 by commit 296f8ca0f73f5268cd9b85cf72ff783596b2264e.
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 update the Linux Kernel to the fixed version.
Conclusion
The HID bigben driver in the Linux Kernel was vulnerable to a slab-out-of-bounds write issue. This vulnerability has been fixed in Linux Kernel version v5.10.121. It is crucial to update the Linux Kernel to the fixed version to ensure system security. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption, system crashes, privilege escalation, or the execution of arbitrary code.
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 the playground will analyze it for vulnerabilities.
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.
The details of remote exploitation are not provided in the vulnerability report. However, it is recommended to update the Linux Kernel to the fixed version to ensure system security.
The vulnerability details do not mention any specific prerequisites for exploitation. Updating the Linux Kernel to the fixed version is the recommended course of action.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
