Deadlock in Concurrent Rename Whiteout and Inode Writeback in ubifs

Kernel Updated 02 Oct 2025

Summary

24/04/2022

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2022-1001119: ubifs: Fix deadlock in concurrent rename whiteout and inode writeback. Affects Kernel versions >= 9e0a1fff8db56eaaebb74b4a3ef65f86811c4798, < 8b278c8dcfb565cb65eceb62a38cbf7a7c326db5. 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 Browse

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.

Background

The ubifs package is a file system designed for use on flash devices. It is a part of the Linux Kernel ecosystem. The package provides a file system that is optimized for flash memory, offering features such as wear-leveling and garbage collection. However, a vulnerability has been discovered in the package that can lead to a deadlock when there is concurrent rename whiteout and inode writeback.

Vulnerability Detail

The vulnerability in ubifs arises when there is concurrent activity involving rename whiteout and inode writeback. This can result in a deadlock situation, where multiple processes or threads are unable to proceed due to conflicting resource access. The deadlock can potentially lead to system instability or unresponsiveness. The vulnerability was introduced in version v4.9 of the Linux Kernel and has been fixed in version v5.17.2.

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 specific workaround available for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

Conclusion

In conclusion, the ubifs package in the Linux Kernel is vulnerable to a deadlock issue when there is concurrent rename whiteout and inode writeback. This vulnerability can be fixed by updating the Linux Kernel to version v5.17.2 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →