UAF in blk_trace access after removing by sysfs in Kernel
Summary
GSD-2021-1001568: blktrace: Fix uaf in blk_trace access after removing by sysfs. Affects Kernel versions >= c71a896154119f4ca9e89d6078f5f63ad60ef199, < 677e362ba807f3aafe6f405c07e0b37244da5222. 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 a bridge between hardware and software. It manages system resources, facilitates communication between different software components, and handles input/output operations. The blktrace module within the Kernel allows users to trace block I/O events and collect performance data for storage devices. However, a vulnerability has been identified in the blktrace module that can lead to a use-after-free (UAF) condition when accessing blk_trace after it has been removed by sysfs.
Vulnerability Detail
The UAF vulnerability in blktrace arises when accessing blk_trace after it has been removed by sysfs. This can occur due to improper handling of the removal process, leading to a situation where the blk_trace structure is accessed even though it has been deallocated. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet.
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 available for this vulnerability. It is essential to update the Kernel to the fixed version to address the issue effectively.
Conclusion
The UAF vulnerability in blktrace, which allows for access to blk_trace after it has been removed by sysfs, poses a potential security risk. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v4.19.209 or later. This fix ensures that the vulnerable code is patched, reducing the risk of exploitation. For additional support and guidance, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's capabilities and the specific system configuration. It could potentially lead to arbitrary code execution or a denial-of-service (DoS) condition.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation. Simply upload your manifest file (e.g., package-lock.json) to the Vulert Playground and it will provide information on any vulnerabilities present in your software.
At the time of this report, no known exploits for this vulnerability have been identified. However, it is crucial to apply the recommended fix to mitigate the risk.
The exact attack vector and exploitability of this vulnerability have not been proven yet. However, remote exploitation may be possible depending on the system's network configuration and the presence of other vulnerabilities.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
