UAF in blk_trace access after removing by sysfs in Kernel
Summary
GSD-2021-1001501: blktrace: Fix uaf in blk_trace access after removing by sysfs. Affects Kernel versions >= c71a896154119f4ca9e89d6078f5f63ad60ef199, < 488da313edf3abea7f7733efe011c96b23740ab5. 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 interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the security and stability of the system. The blktrace module within the Kernel allows users to trace block I/O events and analyze storage performance. However, a vulnerability has been identified in the blktrace module that could 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
No specific workaround has been provided for this vulnerability.
Conclusion
The UAF vulnerability in blktrace, which allows access to blk_trace after it has been removed by sysfs, poses a potential security risk in the Linux Kernel. To mitigate this vulnerability, it is crucial to update the Kernel to version v4.4.286 or later. This update ensures that the vulnerable code is replaced with the patched version, eliminating the UAF vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this UAF vulnerability in the Kernel.
Yes, a patch for this vulnerability is available in the Linux Kernel version v4.4.286 and later. It is recommended to update to the latest version of the Kernel to ensure the vulnerability is addressed.
The remote exploitability of this vulnerability has not been determined yet. However, it is always recommended to apply security patches and updates to mitigate potential risks.
There are no known instances of this vulnerability being exploited in the wild. However, it is important to stay vigilant and apply necessary security updates to protect against potential attacks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
