CVE-2023-54311

ext4: fix deadlock when converting an inline directory in nojournal mode

N/A
Published: December 30, 2025 at 12:23 PM UTC
Updated: June 17, 2026 at 06:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock when converting an inline directory in nojournal mode In no journal mode, ext4_finish_convert_inline_dir() can self-deadlock by calling ext4_handle_dirty_dirblock() when it already has taken the directory lock. There is a similar self-deadlock in ext4_incvert_inline_data_nolock() for data files which we'll fix at the same time. A simple reproducer demonstrating the problem: mke2fs -Fq -t ext2 -O inline_data -b 4k /dev/vdc 64 mount -t ext4 -o dirsync /dev/vdc /vdc cd /vdc mkdir file0 cd file0 touch file0 touch file1 attr -s BurnSpaceInEA -V abcde . touch supercalifragilisticexpialidocious

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8 ≤ v < 5.10.1803.8 ≤ v < 5.15.1123.8 ≤ v < 5.4.2433.8 ≤ v < 6.1.293.8 ≤ v < 6.2.163.8 ≤ v < 6.3.33.8 ≤ v < 6.43.83c47d54170b6a678875566b1b8d6dcf57904e49b
Vendor states this is fixed in 0b1c4357bb21d9770451a1bdb8d419ea10bada88 (fixed)
Vendor states this is fixed in 5f8b55136ad787aed2c184f7cb3e93772ae637a3 (fixed)
Vendor states this is fixed in 640c8c365999c6f23447ac766437236ad88317c5 (fixed)
Vendor states this is fixed in 665cc3ba50330049524c1d275bc840a8f28dde73 (fixed)
Vendor states this is fixed in 804de0c72cd473e186ca4e1f6287d45431b14e5a (fixed)
Vendor states this is fixed in b4fa4768c9acff77245d672d855d2c88294850b1 (fixed)
Vendor states this is fixed in f4ce24f54d9cca4f09a395f3eecce20d6bec4663 (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.112 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.29 (unaffected)
Vendor states this is fixed in 6.2.16 (unaffected)
Vendor states this is fixed in 6.3.3 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card