Deadlock in Concurrent Rename Whiteout and Inode Writeback in ubifs

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002209: ubifs: Fix deadlock in concurrent rename whiteout and inode writeback. Affects Kernel versions >= 9e0a1fff8db56eaaebb74b4a3ef65f86811c4798, < 37bdf1ad592555ecda1d55b89f6e393e4c0589d1. 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 ubifs package is a file system designed for use on flash memory devices. It is commonly used in embedded systems and provides features such as wear-leveling and compression. The vulnerability in ubifs arises when there is concurrent activity involving the renaming of a whiteout file and the writeback of an inode. This can lead to a deadlock situation, where multiple processes are unable to proceed due to conflicting resource access.

Vulnerability Detail

The vulnerability occurs due to a race condition in the ubifs file system. When multiple processes attempt to rename a whiteout file and write back an inode simultaneously, they can end up waiting for each other indefinitely, resulting in a deadlock. This can potentially disrupt the normal operation of the file system and lead to resource exhaustion. The vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.4.189.

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 necessary to apply the fix by updating the Linux Kernel.

Conclusion

The vulnerability in ubifs that causes a deadlock in concurrent rename whiteout and inode writeback has been identified and fixed in Linux Kernel version v5.4.189. Users are advised to update their Linux Kernel to the latest 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

ubifs is a file system designed for use on flash memory devices. It provides features such as wear-leveling and compression, making it suitable for embedded systems.

The vulnerability arises when there is concurrent activity involving the renaming of a whiteout file and the writeback of an inode. This can lead to a deadlock situation.

A deadlock is a situation where multiple processes are unable to proceed because each is waiting for a resource that is held by another process.

The vulnerability can disrupt the normal operation of the file system and lead to resource exhaustion.

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

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