Memory leaks in error handling path of 'log_replay()' in fs/ntfs3

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003174: fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()'. Affects Kernel versions >= b46acd6a6a627d876898e1c84d3f84902264b445, < bc4a1d384a04c6dba9312e1421a9f9f7c03339a4. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fs/ntfs3 package is a component of the Linux Kernel. It provides support for the NTFS file system, allowing Linux systems to read and write to NTFS partitions. The 'log_replay()' function in fs/ntfs3 is responsible for replaying the NTFS transaction log during file system recovery. This function is critical for maintaining the integrity of the file system and ensuring data consistency.

Vulnerability Detail

The vulnerability identified as GSD-2022-1003174 in fs/ntfs3 involves memory leaks in an error handling path of the 'log_replay()' function. When certain error conditions occur during log replay, memory allocated for data structures may not be properly freed, resulting in memory leaks. This can lead to a gradual depletion of system memory resources, potentially causing performance degradation or even system instability. An attacker with local access to the affected system may be able to exploit this vulnerability to exhaust system memory and launch denial-of-service attacks.

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 the impact of this vulnerability by disabling the NTFS file system or preventing access to NTFS partitions. This can be achieved by unmounting NTFS partitions or modifying the system configuration to prevent the loading of the ntfs3 module.

Conclusion

The memory leaks in the error handling path of 'log_replay()' in fs/ntfs3 can have serious consequences for system performance and stability. It is crucial to update the Linux Kernel to version v5.17.14 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

fs/ntfs3 is a component of the Linux Kernel that provides support for the NTFS file system, allowing Linux systems to read and write to NTFS partitions.

'log_replay()' is a function in fs/ntfs3 responsible for replaying the NTFS transaction log during file system recovery.

Memory leaks occur when allocated memory is not properly freed, resulting in a gradual depletion of system memory resources.

The memory leaks in 'log_replay()' can lead to performance degradation or system instability due to the gradual depletion of system memory resources.

To fix the vulnerability, users should update their Linux Kernel to version v5.17.14 or later by downloading the latest kernel source code and compiling it.

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