UAF in blk_trace Access After Removing by sysfs in Kernel
Summary
GSD-2021-1001540: blktrace: Fix uaf in blk_trace access after removing by sysfs. Affects Kernel versions >= c71a896154119f4ca9e89d6078f5f63ad60ef199, < d56171d9360c0170c5c5f8f7e2362a2e999eca40. 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 processes, and handles device drivers. The blktrace module in the Kernel allows users to trace block I/O events and collect performance data for storage devices. This vulnerability affects the blktrace module when accessing blk_trace after it has been removed by sysfs.
Vulnerability Detail
The vulnerability arises due to a use-after-free (UAF) bug in the blktrace module. When blk_trace is accessed after being removed by sysfs, it can lead to memory corruption or crashes. An attacker could potentially exploit this vulnerability to execute arbitrary code, escalate privileges, or cause denial-of-service conditions. The vulnerability was introduced in version v2.6.30 of the Linux Kernel and is fixed in version v4.14.249.
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 in blk_trace access after removing by sysfs vulnerability in the Kernel can lead to memory corruption, crashes, and potential security risks. It is crucial to update the Linux Kernel to version v4.14.249 or later to mitigate this vulnerability. For further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code, escalate privileges, or cause denial-of-service conditions.
You can use the Vulert playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will analyze and alert you in real-time if the vulnerability is present.
Yes, a patch is available in the Linux Kernel version v4.14.249. It is recommended to update your Kernel to this version or later to fix the vulnerability.
The exact attack vector and exploitability of this vulnerability have not been proven. However, if successfully exploited, it could potentially be triggered remotely.
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.
