CVE-2023-54311 json
ext4: fix deadlock when converting an inline directory in nojournal mode
published 10mo ago modified 4mo ago also EUVD-2023-60493
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16, 6.3.3, 6.4
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.7-1
debian advisories DEBIAN-CVE-2023-54311
- linux Ubuntu 20.04 LTS 5.4.0-162.179
- linux Ubuntu 22.04 LTS 5.15.0-83.92
- linux-aws Ubuntu 20.04 LTS 5.4.0-1109.118
- linux-aws Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1112.121
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1041.49
- linux-gke Ubuntu 22.04 LTS 5.15.0-1041.46
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1056.61
ubuntu advisories UBUNTU-CVE-2023-54311
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
- kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1
- kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1
suse advisories SUSE-SU-2026:0617-1SUSE-SU-2026:0473-1SUSE-SU-2026:0411-1SUSE-SU-2026:0317-1SUSE-SU-2026:0263-1
- git.kernel.org/stable/c/b4fa4768c9acff77245d672d855d2c88294850b1 commit
- git.kernel.org/stable/c/5f8b55136ad787aed2c184f7cb3e93772ae637a3 commit
- git.kernel.org/stable/c/640c8c365999c6f23447ac766437236ad88317c5 commit
- git.kernel.org/stable/c/665cc3ba50330049524c1d275bc840a8f28dde73 commit
- git.kernel.org/stable/c/0b1c4357bb21d9770451a1bdb8d419ea10bada88 commit
- git.kernel.org/stable/c/804de0c72cd473e186ca4e1f6287d45431b14e5a commit
- git.kernel.org/stable/c/f4ce24f54d9cca4f09a395f3eecce20d6bec4663 commit
Is CVE-2023-54311 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54311 updated cvss 6.2
kernel: ext4: fix deadlock when converting an inline directory in nojournal mode
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-16).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b4fa4768c9acff77245d672d855d2c88294850b1
- git.kernel.org /stable/c/5f8b55136ad787aed2c184f7cb3e93772ae637a3
- git.kernel.org /stable/c/640c8c365999c6f23447ac766437236ad88317c5
- git.kernel.org /stable/c/665cc3ba50330049524c1d275bc840a8f28dde73
- git.kernel.org /stable/c/0b1c4357bb21d9770451a1bdb8d419ea10bada88
- git.kernel.org /stable/c/804de0c72cd473e186ca4e1f6287d45431b14e5a
- git.kernel.org /stable/c/f4ce24f54d9cca4f09a395f3eecce20d6bec4663
Sources
- CVE List CVE-2023-54311
- NVD CVE-2023-54311
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.