Vulnerability in Kernel: scsi: target: tcmu: Avoid holding XArray lock when calling lock_page
Summary
GSD-2022-1002833: scsi: target: tcmu: Avoid holding XArray lock when calling lock_page. Affects Kernel versions >= e215f411d07d7c618ab3975f9d7e9a89739e86bf, < 607c9c579fcac2d8c8542079121f2ac05ca5f535. 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 software components, and ensures the overall stability and security of the system. The scsi target subsystem in the Kernel is responsible for handling SCSI (Small Computer System Interface) commands and managing storage devices.
One specific component of the scsi target subsystem is tcmu, which stands for Target Core Modem Userspace. Tcmu allows userspace applications to emulate SCSI devices and handle I/O requests. It provides a flexible framework for implementing storage targets in user space.
However, a vulnerability has been discovered in the tcmu component that can potentially lead to security issues.
Vulnerability Detail
The vulnerability in the tcmu component of the Kernel involves holding the XArray lock when calling lock_page. This can result in a deadlock situation, where multiple threads or processes are waiting for each other to release locks, causing the system to become unresponsive.
The vulnerability can be exploited by an attacker to cause a denial-of-service (DoS) condition, rendering the affected system unusable. It may also be possible for an attacker with local access to escalate privileges or execute arbitrary code.
The vulnerability was introduced in version v5.18.3 of the Linux Kernel by commit e215f411d07d7c618ab3975f9d7e9a89739e86bf. It has been fixed in version v5.18.3 by commit 607c9c579fcac2d8c8542079121f2ac05ca5f535.
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 available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
In conclusion, a vulnerability has been identified in the tcmu component of the Kernel, which can lead to a denial-of-service condition and potential privilege escalation or code execution. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) condition, where the affected system becomes unresponsive. It may also allow an attacker with local access to escalate privileges or execute arbitrary code.
You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your software's manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.
Yes, the vulnerability has been fixed in version v5.18.3 of the Linux Kernel. It is recommended to update to this version or later to apply the patch.
No, this vulnerability requires local access to the system to be exploited.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
