Sanity check block descriptor length in resp_mode_select() vulnerability in Kernel
Summary
GSD-2021-1002640: scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select(). Affects Kernel versions < 90491283b4064220682e4b0687d07b05df01e3bf. 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 vulnerability in question affects the Kernel's scsi_debug module, which is responsible for emulating a SCSI device for testing purposes. The resp_mode_select() function within scsi_debug lacks a proper sanity check for the block descriptor length, potentially leading to security vulnerabilities.
Vulnerability Detail
The vulnerability arises from the absence of a thorough block descriptor length validation in the resp_mode_select() function of the scsi_debug module. This oversight could allow an attacker to manipulate the block descriptor length, leading to various security issues. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v4.14.259 by commit 90491283b4064220682e4b0687d07b05df01e3bf.
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
As this vulnerability has been fixed in the Linux Kernel, there is no specific workaround available. It is advised to update the Kernel to the recommended version.
Conclusion
The sanity check block descriptor length vulnerability in the resp_mode_select() function of the scsi_debug module in the Kernel could potentially lead to security issues. It is crucial to update the Linux Kernel to version v4.14.259 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, if exploited, it could potentially lead to security issues.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
Yes, the vulnerability has been fixed in Linux Kernel version v4.14.259 by commit 90491283b4064220682e4b0687d07b05df01e3bf. It is recommended to update the Kernel to this version or later.
There are no known exploits for this vulnerability at the moment.
You can find more information about this vulnerability in the GSD database entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/GSD-2021-1002640.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
