Vulnerability in f2fs: fix to clear dirty inode in f2fs_evict_inode()

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003694: f2fs: fix to clear dirty inode in f2fs_evict_inode(). Affects Kernel versions < 54c116615c99e22aa08aa950757ed726e2f60821. 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 f2fs package is a file system designed for flash-based storage devices in the Linux Kernel. It provides efficient data management and supports various features for improved performance and reliability. However, a vulnerability has been discovered in the package that affects the handling of dirty inodes during eviction.

Vulnerability Detail

The vulnerability arises from a failure to clear dirty inodes in the f2fs_evict_inode() function. This can lead to inconsistent data states and potential data corruption. An attacker could potentially exploit this vulnerability to manipulate or corrupt data on the affected file system. The vulnerability has been addressed in Linux Kernel version v5.4.198 by commit 54c116615c99e22aa08aa950757ed726e2f60821.

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 by updating the Linux Kernel.

Conclusion

In conclusion, the f2fs package in the Linux Kernel is vulnerable to a flaw that can result in data corruption. It is recommended to update the Linux Kernel to version v5.4.198 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

f2fs is a file system designed for flash-based storage devices in the Linux Kernel. It provides efficient data management and supports various features for improved performance and reliability.

The vulnerability can lead to inconsistent data states and potential data corruption on the affected file system.

To fix this vulnerability, update the Linux Kernel to version v5.4.198 or later.

No, there is no known workaround for this vulnerability. It is crucial to apply the fix by updating the Linux Kernel.

For more details about this vulnerability, refer to the provided references link.

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