f2fs: Fix Sanity Check on Block Address in f2fs_do_zero_range()

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002950: f2fs: fix to do sanity check on block address in f2fs_do_zero_range(). Affects Kernel versions < 470493be19a5730ed432e3ac0f29a2ee7fc6c557. 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 f2fs package is a file system designed for flash-based storage devices in the Linux Kernel. It provides efficient data management and wear-leveling algorithms to optimize performance and extend the lifespan of flash memory. However, a vulnerability has been discovered in the f2fs_do_zero_range() function, which could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the f2fs_do_zero_range() function arises from a lack of sanity checks on the block address parameter. An attacker could exploit this vulnerability by providing a malicious block address, leading to unexpected behavior or even a system crash. The impact of this vulnerability may vary depending on the specific usage scenario, but it has the potential to allow an attacker to gain unauthorized access or disrupt the normal operation 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 avoid potential exploitation of this vulnerability by avoiding the use of the f2fs_do_zero_range() function or by implementing additional input validation checks on the block address parameter before calling the function. Here is an example of how to perform the input validation check in C:

if (block_address < 0 || block_address >= total_blocks) {
    // Handle invalid block address
}

Conclusion

In conclusion, the f2fs package in the Linux Kernel is vulnerable to a security issue in the f2fs_do_zero_range() function. It is crucial to update the Linux Kernel to version v5.17.14 or later to mitigate this vulnerability. Additionally, implementing input validation checks or avoiding the use of the affected function can serve as temporary workarounds. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability may vary depending on the specific usage scenario, but it has the potential to allow an attacker to gain unauthorized access or disrupt the normal operation of the system.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.14 or later, which includes the necessary fix commit.

Yes, as a temporary workaround, users can avoid potential exploitation of this vulnerability by avoiding the use of the f2fs_do_zero_range() function or by implementing additional input validation checks on the block address parameter before calling the function.

Certainly! Here is an example of how to perform the input validation check in C:

if (block_address < 0 || block_address >= total_blocks) {
    // Handle invalid block address
}

For more information about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.

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