Memory Leak Vulnerability in nilfs2 Kernel Package

Kernel Updated 02 Oct 2025

Summary

08/07/2021
N/A
No i
Unrated
Not published

UVI-2021-1001134: nilfs2: fix memory leak in nilfs_sysfs_delete_device_group. Affects Kernel versions >= da7141fb78db915680616e15677539fc8140cf53, < 2eb327bf4de3d1713496f231ea7ede5e4df06458. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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. However, a memory leak vulnerability has been discovered in the nilfs_sysfs_delete_device_group function of the nilfs2 package.

Vulnerability Detail

The memory leak vulnerability in nilfs2 arises when the nilfs_sysfs_delete_device_group function is called. This function is responsible for deleting a device group from the sysfs file system. However, due to a coding error, memory allocated during the deletion process is not properly freed, leading to a memory leak. An attacker could potentially exploit this vulnerability by repeatedly triggering the deletion of device groups, causing the system to exhaust available memory resources. This could result 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

As a workaround, users can avoid triggering the vulnerability by refraining from deleting device groups using the sysfs interface. Instead, alternative methods for managing device groups should be employed until the kernel update can be applied.

Conclusion

In conclusion, the nilfs2 package in the Linux Kernel is affected by a memory leak vulnerability in the nilfs_sysfs_delete_device_group function. This vulnerability can be mitigated by updating the kernel to version v5.12.14 or later. Until the update is applied, users can employ the provided workaround to avoid triggering the vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a memory leak, potentially causing a denial-of-service condition or other unpredictable behavior.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze and alert you if the vulnerability is present.

At the time of this report, there are no known exploits for this vulnerability. However, it is still important to apply the recommended fix to prevent potential exploitation.

No, this vulnerability requires local access to the system in order to trigger the deletion of device groups and exploit the memory leak.

Yes, you can find more details about this vulnerability in the Open Source Vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is UVI-2021-1001134.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback