Memory Leak Vulnerability in fs/ntfs3 Package

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002861: fs/ntfs3: provide block_invalidate_folio to fix memory leak. Affects Kernel versions >= 7ba13abbd31ee9265e88d7dc029c0f786e665192, < 0753245a72ec99824677586499ee2e0919164b3f. 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 fs/ntfs3 package is a component of the Linux Kernel ecosystem. It provides support for the NTFS file system, allowing Linux systems to read and write to NTFS partitions. The package is responsible for handling various file system operations and ensuring compatibility with NTFS. However, a vulnerability has been discovered in the package that can lead to a memory leak.

Vulnerability Detail

The vulnerability in the fs/ntfs3 package is related to a missing function called 'block_invalidate_folio'. This function is responsible for invalidating file system blocks, ensuring that they are not used after being freed. Without this function, a memory leak can occur, where freed blocks are not properly released, leading to a gradual depletion of available memory. This vulnerability can potentially impact the stability and performance of the system, as well as open up opportunities for attackers to exploit the memory leak for malicious purposes.

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

If updating the Linux Kernel is not immediately feasible, a temporary workaround can be implemented. This workaround involves manually adding the missing 'block_invalidate_folio' function to the fs/ntfs3 package. Here is an example of the code that needs to be added:

void block_invalidate_folio(struct folio *folio) {
  // Implementation code goes here
}

By adding this function, the memory leak can be mitigated until a proper kernel update is applied.

Conclusion

The memory leak vulnerability in the fs/ntfs3 package can have significant implications for system stability and performance. It is crucial to update the Linux Kernel to version v5.18.3 or later to address this issue. In the meantime, a temporary workaround is available by manually adding the missing 'block_invalidate_folio' function. For more information 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, causing gradual depletion of available memory. This can impact system stability and performance.

To fix this vulnerability, update the Linux Kernel to version v5.18.3 or later, which includes the necessary fix.

Yes, a temporary workaround involves manually adding the missing 'block_invalidate_folio' function to the fs/ntfs3 package. See the 'workaround' section for more details.

At the time of this report, no known exploits have been identified. However, it is crucial to apply the recommended fix to prevent potential exploitation.

For more information, you can refer to the vulnerability details in the Open Source Vulnerability format. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

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