f2fs: Inline Inode Sanity Check Vulnerability in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003245: f2fs: fix to do sanity check for inline inode. Affects Kernel versions < 7cfe2d43becaf76e562b9617d2c2d9b445f86761. 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 (Flash-Friendly File System) is a file system designed specifically for NAND-based flash memory storage devices. It is part of the Linux Kernel and provides features like wear-leveling, garbage collection, and TRIM support. The inline inode feature in f2fs allows small files to be stored directly within the inode structure, improving performance for small file operations. However, a vulnerability exists in the inline inode implementation that could be exploited by an attacker.

Vulnerability Detail

The f2fs inline inode vulnerability arises due to a lack of proper sanity checks during file operations. An attacker could craft a malicious file that triggers a buffer overflow or other memory corruption issues, potentially leading to arbitrary code execution or a denial of service. This vulnerability could be exploited by an attacker with local access to the system or through a remote code execution vulnerability in another component.

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 provided fix by updating the Linux Kernel to a patched version.

Conclusion

The f2fs inline inode sanity check vulnerability in the Linux Kernel could allow an attacker to execute arbitrary code or cause a denial of service. It is crucial to update the Kernel to a patched version to mitigate the risk. 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 NAND-based flash memory storage devices. It provides features like wear-leveling, garbage collection, and TRIM support.

An inline inode is a feature in f2fs that allows small files to be stored directly within the inode structure, improving performance for small file operations.

This vulnerability could be exploited to execute arbitrary code or cause a denial of service on a system running the affected version of the Linux Kernel.

An attacker with local access to the system or through a remote code execution vulnerability in another component could potentially exploit this vulnerability.

To fix this vulnerability, update the Linux Kernel to version v5.15.46 or later, which includes the necessary fix for the f2fs inline inode 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