Vulnerability in f2fs Package: SBI_NEED_FSCK Flag Setting

Kernel Updated 02 Oct 2025

Summary

19/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002480: f2fs: set SBI_NEED_FSCK flag when inconsistent node block found. Affects Kernel versions < 22423c966e02175a45bc010134d734e920b76cdf. 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 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 package that involves the incorrect setting of the SBI_NEED_FSCK flag when an inconsistent node block is found. This flag is used to indicate the need for a file system check (fsck) to repair any inconsistencies in the file system structure.

Vulnerability Detail

The vulnerability arises when the f2fs package fails to set the SBI_NEED_FSCK flag appropriately upon encountering an inconsistent node block. This can lead to potential issues with the file system's integrity and reliability. Attackers may exploit this vulnerability to manipulate or corrupt data, cause system crashes, or execute arbitrary code. The impact and attack plausibility of this vulnerability have not been proven yet.

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 specific workaround mentioned for this vulnerability.

Conclusion

The f2fs package in the Linux kernel is vulnerable to an issue where the SBI_NEED_FSCK flag is not set correctly when an inconsistent node block is encountered. This vulnerability can have serious implications for the integrity and reliability of the file system. It is recommended to update the Linux kernel to version v5.10.83 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

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.

The SBI_NEED_FSCK flag is used in the f2fs package to indicate the need for a file system check (fsck) to repair any inconsistencies in the file system structure.

The impact of this vulnerability can include data manipulation or corruption, system crashes, and potential execution of arbitrary code.

To fix this vulnerability, update the Linux kernel to version v5.10.83 or later, which includes the necessary fix for setting the SBI_NEED_FSCK flag correctly.

No specific workaround has been mentioned for this vulnerability.

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