Vulnerability in Kernel: block: don't call rq_qos_ops->done_bio if the bio isn't tracked
Summary
GSD-2021-1001700: block: don't call rq_qos_ops->done_bio if the bio isn't tracked. Affects Kernel versions < 004b8f8a691205a93d9e80d98b786b2b97424d6e. 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 provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different components, and handles input/output operations. The vulnerability in question affects the block subsystem of the Kernel, which is responsible for managing block devices such as hard drives and SSDs. This vulnerability specifically pertains to the handling of tracked bios in the block subsystem.
Vulnerability Detail
The vulnerability arises from a flaw in the block subsystem's handling of bios that are not tracked. In certain scenarios, the subsystem erroneously calls rq_qos_ops->done_bio even when the bio is not being tracked. This can lead to unexpected behavior and potential security risks. While the impact and attack plausibility have not been proven, it is crucial to address this vulnerability to ensure the integrity and security of the system.
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 mentioned for this vulnerability. It is advised to apply the fix by updating the Kernel as mentioned in the 'how_to_fix' section.
Conclusion
In conclusion, the vulnerability in the Kernel's block subsystem can lead to unexpected behavior and potential security risks. It is crucial to update the Kernel to version v5.14.11 or later to mitigate this vulnerability. By applying the recommended fix, you can ensure the integrity and security of your system. For additional support and guidance, feel free to contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, it has the potential to result in unexpected behavior and security risks in the affected system.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
As of now, there is no known exploit for this vulnerability. However, it is essential to address it promptly by updating the Kernel to the fixed version to prevent any potential exploitation.
The specific prerequisites for exploiting this vulnerability are not mentioned. However, it is always recommended to keep the system up to date with the latest security patches and updates to minimize the risk of exploitation.
For further support and assistance in vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be glad to assist you in addressing the vulnerability and ensuring the security of your system.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
