Memory Leak in nilfs_sysfs_delete_device_group in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-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 Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. The nilfs2 file system is a specific file system implemented within the Kernel. It is designed to provide continuous snapshotting capabilities, allowing users to revert to previous versions of files or directories. However, a vulnerability has been discovered in the nilfs_sysfs_delete_device_group function, which can lead to a memory leak issue.

Vulnerability Detail

The vulnerability, identified as GSD-2021-1001134, originates from a memory leak in the nilfs_sysfs_delete_device_group function within the nilfs2 file system. When this function is called to delete a device group, it fails to release allocated memory, resulting in a memory leak. This can potentially exhaust system resources and lead to performance degradation or even system instability. The vulnerability was introduced in version v3.17 of the Linux Kernel and has been fixed in version v5.12.14.

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 avoid triggering the nilfs_sysfs_delete_device_group function by refraining from deleting device groups in the nilfs2 file system. However, this workaround is not a permanent solution and should only be considered until the Kernel is updated to a fixed version.

Conclusion

In conclusion, the nilfs_sysfs_delete_device_group function in the nilfs2 file system within the Linux Kernel is vulnerable to a memory leak issue. This vulnerability can lead to resource exhaustion and potential system instability. It is crucial to update the Kernel to version v5.12.14 or later to mitigate this vulnerability. Users can also utilize the Vulert Playground to check if their system is affected. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in a memory leak, leading to resource exhaustion and potential system instability or performance degradation.

You can utilize the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix to mitigate any potential risks.

Yes, it is possible to manually patch the Kernel source code to fix this vulnerability. However, this requires advanced knowledge and understanding of the Kernel's internal workings. It is recommended to follow the official update process or wait for the distribution-specific updates.

While there are alternative file systems available, it is not recommended to switch file systems as a temporary replacement for this vulnerability. It is best to apply the official fix provided by the Linux Kernel developers.

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