linux-cve-announce - CVE-2023-53129: ext4: Fix deadlock during directory rename

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025050234-CVE-2023-53129-038a@gregkh>
Date: Fri,  2 May 2025 17:56:34 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53129: ext4: Fix deadlock during directory rename

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ext4: Fix deadlock during directory rename

As lockdep properly warns, we should not be locking i_rwsem while having
transactions started as the proper lock ordering used by all directory
handling operations is i_rwsem -> transaction start. Fix the lock
ordering by moving the locking of the directory earlier in
ext4_rename().

The Linux kernel CVE team has assigned CVE-2023-53129 to this issue.


Affected and fixed versions
===========================

	Issue fixed in mainline with commit 3c92792

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53129
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/ext4/namei.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/6b06c4ae64e3557a19b3bb0b6dbf641bc41fc218
	https://git.kernel.org/stable/c/b113f90204479f55a17295bedf0cc966a60c7a56
	https://git.kernel.org/stable/c/a2bc806e95bde8de3a0d675051d9ae78dcf6c691
	https://git.kernel.org/stable/c/2ef7f829214fa8f428d953b49557b89b2b02db66
	https://git.kernel.org/stable/c/352c728653a1179ce7bb37a4c8aa8404d83914a2
	https://git.kernel.org/stable/c/3c92792da8506a295afb6d032b4476e46f979725