Vulnerability in f2fs: fix to do sanity check on curseg->alloc_type

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001151: f2fs: fix to do sanity check on curseg->alloc_type. Affects Kernel versions < c12765e3f129b144421c80d3383df885f85ee290. 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 techniques to optimize performance and longevity of flash storage. However, a vulnerability has been discovered in the package that could potentially be exploited by attackers.

Vulnerability Detail

The vulnerability in the f2fs package arises from a missing sanity check on the curseg->alloc_type parameter. This oversight could lead to memory corruption or other unexpected behavior, potentially allowing an attacker to execute arbitrary code or crash the system. The impact and attack plausibility of this vulnerability have not yet been proven, but it is important to address it to ensure the security and stability of the system.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.2 or later. This fix is implemented in commit c12765e3f129b144421c80d3383df885f85ee290. Updating the kernel will ensure that the necessary sanity check is performed on the curseg->alloc_type parameter, mitigating the 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. The recommended course of action is to apply the fix by updating the Linux Kernel.

Conclusion

The vulnerability in the f2fs package can be addressed by updating the Linux Kernel to version v5.17.2 or later. This will ensure the necessary sanity check is performed on the curseg->alloc_type parameter, mitigating the vulnerability. For further support on vulnerability remediation, you can reach out to 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 wear-leveling techniques to optimize performance and longevity of flash storage.

The impact of this vulnerability is not yet proven, but it could potentially lead to memory corruption or other unexpected behavior, allowing an attacker to execute arbitrary code or crash the system.

To fix this vulnerability, update the Linux Kernel to version v5.17.2 or later, which includes the necessary fix for the missing sanity check on the curseg->alloc_type parameter.

No specific workaround is mentioned for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.

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.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.17.2 or later. This fix is implemented in commit c12765e3f129b144421c80d3383df885f85ee290. Updating the kernel will ensure that the necessary sanity check is performed on the curseg->alloc_type parameter, mitigating the 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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.