Use-after-free vulnerability in ubi_create_volume function in Kernel
Summary
GSD-2022-1003277: ubi: ubi_create_volume: Fix use-after-free when volume creation failed. Affects Kernel versions >= 493cfaeaa0c9bc0c79ce5751193d49fdac9aaaec, < 5ff2514e4fb55dcf3d88294686040ca73ea0c1a2. 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 crucial component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The ubi_create_volume function is responsible for creating volumes in the UBI (Unsorted Block Images) subsystem, which is used for managing flash storage devices. This vulnerability affects the Kernel versions starting from v4.12 and was fixed in v5.15.47.
Vulnerability Detail
The use-after-free vulnerability in the ubi_create_volume function occurs when volume creation fails. This vulnerability can be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. When volume creation fails, the function fails to properly handle the error condition, leading to a use-after-free scenario. This can result in memory corruption and potentially allow an attacker to gain control over the affected system.
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 mentioned for this vulnerability. Users are advised to apply the recommended fix by updating the Kernel to the patched version.
Conclusion
The use-after-free vulnerability in the ubi_create_volume function of the Kernel can lead to arbitrary code execution or denial-of-service. It is crucial to update the Kernel to version v5.15.47 or later to address this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition on the affected system.
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 manifest file (e.g., package-lock.json) and provides real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to the network and the necessary conditions are met. It is crucial to update the Kernel to the patched version to prevent potential remote exploitation.
If you cannot immediately update the Kernel, it is recommended to implement other security measures such as network segmentation, access controls, and intrusion detection systems to reduce the risk of exploitation. However, updating the Kernel to the patched version is the most effective way to mitigate this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
