Read Out-of-Bounds Vulnerability in ubifs
Summary
GSD-2022-1002208: ubifs: Fix read out-of-bounds in ubifs_wbuf_write_nolock(). Affects Kernel versions >= 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d, < b80ccbec0e4804436c382d7dd60e943c386ed83a. 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 in the Linux kernel. It provides wear-leveling and other features specific to flash storage. The vulnerability in ubifs_wbuf_write_nolock() function allows an attacker to read out-of-bounds memory, potentially leading to information disclosure or privilege escalation.
Vulnerability Detail
The vulnerability originates from a read out-of-bounds issue in the ubifs_wbuf_write_nolock() function. This function is responsible for writing data to the ubifs write buffer. By manipulating certain parameters, an attacker can trigger a read operation that goes beyond the bounds of the intended memory region. This can result in the disclosure of sensitive information or the execution of arbitrary code with elevated privileges. The vulnerability was introduced in version v2.6.27 of the Linux kernel and has been fixed in version v5.4.189.
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
As a temporary workaround, users can disable the use of the ubifs file system or switch to an alternative file system that is not affected by this vulnerability. However, this may not be feasible in all cases, especially if the ubifs file system is required for specific use cases.
Conclusion
The read out-of-bounds vulnerability in ubifs can potentially lead to information disclosure or privilege escalation. It is crucial to update the Linux kernel to the fixed version or apply the recommended workarounds to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability allows an attacker to read out-of-bounds memory, potentially leading to information disclosure or privilege escalation.
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 Vulert will analyze it for any known vulnerabilities.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to the internet and the attacker can send malicious requests to trigger the read out-of-bounds operation.
The recommended mitigation is to update the Linux kernel to the fixed version. If updating is not immediately possible, disabling the use of the ubifs file system or switching to an alternative file system can provide temporary protection.
At the time of this report, there is no evidence of active exploits targeting this vulnerability. However, it is always recommended to apply security patches as soon as they become available to minimize the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
