Memory Leak Vulnerability in nilfs2 Package
Summary
UVI-2021-1001119: nilfs2: fix memory leak in nilfs_sysfs_delete_device_group. Affects Kernel versions >= da7141fb78db915680616e15677539fc8140cf53, < d6f751ecccfb7a7b75e038a0ca052138dc52119b. 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 nilfs2 package is a component of the Linux Kernel, which is responsible for managing the NILFS2 file system. NILFS2 is a log-structured file system that provides continuous snapshotting and efficient incremental backup capabilities. It is commonly used in Linux distributions for various applications and storage devices.
Vulnerability Detail
The vulnerability identified as UVI-2021-1001119 in the nilfs2 package is a memory leak issue that occurs during the deletion of a device group in the sysfs interface. This vulnerability was introduced in version v3.17 of the Linux Kernel and affects all subsequent versions until v5.4.129. When the nilfs_sysfs_delete_device_group function is called, it fails to release allocated memory, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, resulting in a denial-of-service condition or other unpredictable behavior.
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 essential to apply the provided fix by updating the Linux Kernel to a patched version.
Conclusion
The memory leak vulnerability in the nilfs2 package can be mitigated by updating the Linux Kernel to version v5.4.129 or later. It is crucial to apply the provided fix to prevent potential denial-of-service conditions or other unpredictable behavior. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a denial-of-service condition or other unpredictable behavior due to memory exhaustion.
No, this vulnerability requires local access to the system.
No, only versions from v3.17 to v5.4.129 are affected. Versions prior to v3.17 and later than v5.4.129 are not vulnerable.
There is no evidence of active exploitation of this vulnerability at the time of this report.
Yes, you can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
