Deadlock Vulnerability in ubifs Package
Summary
GSD-2022-1002032: ubifs: Fix deadlock in concurrent rename whiteout and inode writeback. Affects Kernel versions >= 9e0a1fff8db56eaaebb74b4a3ef65f86811c4798, < 83e42a78428fc354f5e2049935b84c8d8d29b787. 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 ubifs package is a file system designed for use on flash devices. It is commonly used in embedded systems and provides features such as compression and wear-leveling. This vulnerability affects the ubifs package in the Linux Kernel.
Vulnerability Detail
The vulnerability in ubifs arises from a deadlock that can occur when there is concurrent activity involving rename whiteout and inode writeback operations. This can lead to a system deadlock, causing the affected system to become unresponsive. The vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.10.110.
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 for this vulnerability. It is necessary to update the Linux Kernel to the fixed version.
Conclusion
In conclusion, the ubifs package in the Linux Kernel is vulnerable to a deadlock issue when there is concurrent activity involving rename whiteout and inode writeback operations. This can lead to a system deadlock and unresponsiveness. It is recommended to update the Linux Kernel to version v5.10.110 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
ubifs is a file system designed for use on flash devices. It provides features such as compression and wear-leveling.
The vulnerability can lead to a system deadlock, causing the affected system to become unresponsive.
To fix this vulnerability, update the Linux Kernel to version v5.10.110 or later.
No, there is no known workaround. Updating the Linux Kernel is necessary.
Detailed instructions on how to update the Linux Kernel can be found in the official documentation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.