ext4: Fix Use-After-Free Vulnerability in ext4_rename_dir_prepare

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002935: ext4: fix use-after-free in ext4_rename_dir_prepare. Affects Kernel versions < 0ff38b99fa075ddd246487a28cb9af049f4ceef1. 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 ext4 filesystem is a widely used file system in the Linux kernel. It provides support for large file systems and files, journaling, and other advanced features. The ext4_rename_dir_prepare function is responsible for preparing a directory for renaming in the ext4 filesystem. However, a use-after-free vulnerability has been discovered in this function, which could be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition.

Vulnerability Detail

The use-after-free vulnerability in ext4_rename_dir_prepare occurs when the function fails to properly handle a directory entry that is being renamed. This can lead to a situation where a pointer to a freed memory object is still accessible, potentially allowing an attacker to manipulate the memory and execute arbitrary code. The impact of this vulnerability can vary depending on the attacker's capabilities and the specific context in which the vulnerable code is executed. However, it has the potential to result in privilege escalation, data corruption, or system crashes.

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 strongly advised to apply the official fix by updating the Linux kernel.

Conclusion

The use-after-free vulnerability in ext4_rename_dir_prepare can have serious security implications, potentially allowing an attacker to execute arbitrary code or cause system crashes. It is crucial to update the Linux kernel to the latest version that includes the fix for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The ext4 filesystem is a popular file system used in the Linux kernel. It provides support for large file systems and files, journaling, and other advanced features.

The ext4_rename_dir_prepare function is responsible for preparing a directory for renaming in the ext4 filesystem.

A use-after-free vulnerability occurs when a program continues to use a memory object after it has been freed. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code.

The impact of this vulnerability can vary depending on the attacker's capabilities and the specific context in which the vulnerable code is executed. However, it has the potential to result in privilege escalation, data corruption, or system crashes.

To fix this vulnerability, it is recommended to update the Linux kernel to version v5.17.14 or later, which includes the fix for this issue. Users can obtain the updated kernel from the official Linux kernel repository or through their distribution's package management system.

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