Use-After-Free Vulnerability in Linux Kernel f2fs Package

linux Updated 02 Oct 2025

Summary

26/08/2024
N/A
No i
High
7.8

CVE-2024-44941: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to cover read extent cache access with lock syzbot reports a f2fs bug as below: BUG: KASAN: slab-use-after-free in sanity_check_extent_cache+0... Affects linux versions 5.10.103-1 – 6.9.9-1. 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 Linux kernel is a core component of many operating systems, providing essential services for hardware management and system resources. The f2fs (Flash-Friendly File System) is designed to optimize performance on flash storage devices. This file system is widely used in various environments, including mobile devices and embedded systems. However, it has been identified to have a critical vulnerability that can lead to severe security issues.

Vulnerability Detail

In the Linux kernel, specifically within the f2fs file system, a use-after-free vulnerability has been discovered. This issue arises from a failure to properly synchronize access to the extent cache, allowing for potential race conditions. The vulnerability was reported by syzbot, which indicated a slab-use-after-free error during the execution of the sanity_check_extent_cache function. This can lead to unauthorized access to freed memory, potentially allowing attackers to execute arbitrary code or crash the system. The vulnerability is particularly concerning as it affects the integrity and availability of the system, with a CVSS score of 7.8 indicating a high severity level.

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

As a temporary measure, users can avoid triggering the vulnerability by not using the f2fs file system until the kernel is updated. Additionally, ensuring that proper locking mechanisms are in place when accessing the extent cache can mitigate the risk until a fix is applied.

Conclusion

The use-after-free vulnerability in the Linux kernel's f2fs file system poses significant risks to system integrity and security. It is crucial for users to apply the necessary updates to mitigate these risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time, ensuring that systems remain secure.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a memory location after it has been freed, potentially leading to arbitrary code execution or system crashes.

You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json, you can check for vulnerabilities without needing to install any software.

The consequences can include unauthorized access to system memory, execution of arbitrary code, and system instability, which can lead to data loss or service disruption.

Yes, the vulnerability is fixed in version 6.10.6-1 for Debian 13. Users of Debian 11 and 12 should ensure they have the latest security patches.

If an immediate update is not possible, refrain from using the f2fs file system and implement proper locking mechanisms to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

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