Vulnerability in Kernel: ntfs - Sanity Check on Allocation Size

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001788: ntfs: add sanity check on allocation size. Affects Kernel versions < 24ab2d4ef52c2dbb62a60844b87fc8872383407a. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities, such as device drivers, memory management, and process scheduling. The ntfs module within the Kernel enables the support for the NTFS file system commonly used in Windows. This vulnerability specifically affects the ntfs module's handling of allocation size. The allocation size is a parameter that determines the size of disk space allocated for a file or directory. Without proper validation, an attacker could exploit this vulnerability to manipulate the allocation size and potentially cause a denial-of-service or other security issues.

Vulnerability Detail

The vulnerability arises from a lack of sanity check on the allocation size parameter within the ntfs module of the Kernel. By providing a malicious allocation size value, an attacker could trigger unexpected behavior or memory corruption. This could lead to various consequences, including system crashes, data corruption, or even remote code execution. The impact and attack plausibility of this vulnerability have not been fully proven yet, but it is crucial to address it to ensure the security and stability of the system.

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 disable the ntfs module if it is not essential for their system. This can be achieved by removing or blacklisting the module. However, this workaround should only be considered if the ntfs functionality is not required, as it may impact the system's ability to read or write NTFS file systems.

Conclusion

The vulnerability in the ntfs module of the Kernel, which lacks a sanity check on the allocation size parameter, poses potential risks to the system's stability and security. It is crucial to update the Kernel to version v5.15.33 or later to address this vulnerability. In the meantime, if the ntfs functionality is not required, users can consider disabling the module as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can range from system crashes and data corruption to potential remote code execution. However, the exact consequences depend on the attacker's capabilities and the specific system configuration.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known exploit for this vulnerability. However, it is essential to address it promptly by updating the Kernel to prevent any potential exploitation.

While updating the Kernel is the recommended approach, you can temporarily mitigate the vulnerability by disabling the ntfs module if it is not necessary for your system. However, this should only be considered as a temporary workaround until the Kernel can be updated.

Any system that utilizes the ntfs module within the Kernel is potentially vulnerable. However, the impact may vary depending on the specific system configuration and the attacker's capabilities.

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