Vulnerability in f2fs Package: Sanity Check on Block Address

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003702: f2fs: fix to do sanity check on block address in f2fs_do_zero_range(). Affects Kernel versions < 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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 techniques to enhance the lifespan of flash memory. The package is widely used in various Linux distributions and embedded systems.

Vulnerability Detail

The vulnerability identified in the f2fs package involves a lack of sanity check on block addresses in the f2fs_do_zero_range() function. This oversight could potentially lead to out-of-bounds memory access or other memory-related issues. An attacker could exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. The vulnerability was fixed in Linux Kernel version v5.4.198 by commit 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67.

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 essential to apply the fix mentioned above to ensure the security and stability of the system.

Conclusion

The vulnerability in the f2fs package, which lacked a sanity check on block addresses, has been addressed in Linux Kernel version v5.4.198. It is crucial to update the kernel to the fixed version or apply the relevant patches to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service condition.

The vulnerability requires local access to the system. However, if an attacker gains local access, they can exploit the vulnerability.

There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the fix to mitigate any potential risks.

Yes, embedded systems utilizing the f2fs package are also vulnerable to this issue. It is recommended to update the kernel on such systems as well.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will provide real-time alerts for open-source vulnerabilities.

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