Memory Leak in nilfs_sysfs_delete_device_group in nilfs2

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001113: nilfs2: fix memory leak in nilfs_sysfs_delete_device_group. Affects Kernel versions >= da7141fb78db915680616e15677539fc8140cf53, < 9436cdffaf5bc83f41e72dfbd4d9ec885ff7b4f2. 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 file system implemented in the Linux Kernel. It provides support for the NILFS (New Implementation of a Log-structured File System) file system. The NILFS file system is designed to provide continuous snapshotting capability, allowing users to easily recover from system crashes or data corruption. The nilfs_sysfs_delete_device_group function is responsible for deleting a device group in the sysfs interface of the nilfs2 file system.

Vulnerability Detail

The vulnerability identified as GSD-2021-1001113 in the nilfs2 package is a memory leak issue in the nilfs_sysfs_delete_device_group function. This vulnerability was introduced in version v3.17 of the Linux Kernel and fixed in version v4.19.196. The vulnerability occurs when deleting a device group in the sysfs interface, where memory is not properly freed, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, causing a denial-of-service condition.

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 recommended to apply the fix by updating the Linux Kernel.

Conclusion

The memory leak vulnerability in the nilfs_sysfs_delete_device_group function of the nilfs2 package can be fixed by updating the Linux Kernel to version v4.19.196 or later. It is recommended to apply the fix to prevent potential denial-of-service attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

nilfs2 is a file system implemented in the Linux Kernel, providing support for the NILFS (New Implementation of a Log-structured File System) file system.

The nilfs_sysfs_delete_device_group function is responsible for deleting a device group in the sysfs interface of the nilfs2 file system.

A memory leak is a situation where allocated memory is not properly freed, leading to a gradual loss of available memory resources.

The vulnerability could be exploited by an attacker to exhaust system memory resources, causing a denial-of-service condition.

To fix this vulnerability, update the Linux Kernel to version v4.19.196 or later.

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