UAF in blk_trace access after removing by sysfs in Kernel
Summary
GSD-2021-1001610: blktrace: Fix uaf in blk_trace access after removing by sysfs. Affects Kernel versions >= c71a896154119f4ca9e89d6078f5f63ad60ef199, < ebb8d26d93c3ec3c7576c52a8373a2309423c069. 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 functionality 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. However, a vulnerability has been discovered in blktrace that can lead to a use-after-free (UAF) issue when accessing blk_trace after it has been removed by sysfs.
Vulnerability Detail
The vulnerability arises due to improper handling of blk_trace access after it has been removed by sysfs. An attacker could exploit this vulnerability by manipulating the sysfs interface to trigger a use-after-free condition. This could potentially result in a crash, privilege escalation, or the execution of arbitrary code with kernel-level privileges. The vulnerability was introduced in version v2.6.30 of the Kernel and has been fixed in version v5.4.150.
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 for blk_trace access after removal by sysfs, poses a significant risk to the security and stability of Linux systems. It is crucial to update the Linux Kernel to version v5.4.150 or later to address this vulnerability. Failure to do so may result in the exploitation of the vulnerability, leading to potential system compromise. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially allow an attacker to execute arbitrary code with kernel-level privileges, leading to a complete compromise of the affected system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to promptly update the Kernel to the fixed version to mitigate the risk of potential exploitation.
Yes, a patch has been released in version v5.4.150 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.
No, this vulnerability requires a code fix in the Kernel itself. Configuration changes alone will not mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
