linux-cve-announce - CVE-2022-50436: ext4: don't set up encryption key during jbd2 transaction

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: <2025100159-CVE-2022-50436-ad37@gregkh>
Date: Wed,  1 Oct 2025 13:42:09 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50436: ext4: don't set up encryption key during jbd2 transaction

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

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

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

ext4: don't set up encryption key during jbd2 transaction

Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature")
extended the scope of the transaction in ext4_unlink() too far, making
it include the call to ext4_find_entry().  However, ext4_find_entry()
can deadlock when called from within a transaction because it may need
to set up the directory's encryption key.

Fix this by restoring the transaction to its original scope.

The Linux kernel CVE team has assigned CVE-2022-50436 to this issue.


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

	Issue introduced in 5.10 with commit a80f7fcf18672ae4971a6b713b58c0d389aa99fe and fixed in 5.10.163 with commit 23ad034760dd38e12b0e0e1b28b9629f330810a1
	Issue introduced in 5.10 with commit a80f7fcf18672ae4971a6b713b58c0d389aa99fe and fixed in 5.15.87 with commit 6220ec405571ded17efedc56587190b542adf246
	Issue introduced in 5.10 with commit a80f7fcf18672ae4971a6b713b58c0d389aa99fe and fixed in 6.0.18 with commit 206dd3acfb9bca54a25b228c7c7c2257eedde09b
	Issue introduced in 5.10 with commit a80f7fcf18672ae4971a6b713b58c0d389aa99fe and fixed in 6.1.4 with commit 1ba993208bcfd691e241483420a2a761d3f15750
	Issue introduced in 5.10 with commit a80f7fcf18672ae4971a6b713b58c0d389aa99fe and fixed in 6.2 with commit 4c0d5778385cb3618ff26a561ce41de2b7d9de70

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-2022-50436
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/ext4.h
	fs/ext4/fast_commit.c
	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/23ad034760dd38e12b0e0e1b28b9629f330810a1
	https://git.kernel.org/stable/c/6220ec405571ded17efedc56587190b542adf246
	https://git.kernel.org/stable/c/206dd3acfb9bca54a25b228c7c7c2257eedde09b
	https://git.kernel.org/stable/c/1ba993208bcfd691e241483420a2a761d3f15750
	https://git.kernel.org/stable/c/4c0d5778385cb3618ff26a561ce41de2b7d9de70