linux-cve-announce - CVE-2022-50126: jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted

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: <2025061813-CVE-2022-50126-5c77@gregkh>
Date: Wed, 18 Jun 2025 13:03:11 +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-50126: jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted

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

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

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

jbd2: fix assertion 'jh->b_frozen_data == NULL' failure when journal aborted

Following process will fail assertion 'jh->b_frozen_data == NULL' in
jbd2_journal_dirty_metadata():

                   jbd2_journal_commit_transaction
unlink(dir/a)
 jh->b_transaction = trans1
 jh->b_jlist = BJ_Metadata
                    journal->j_running_transaction = NULL
                    trans1->t_state = T_COMMIT
unlink(dir/b)
 handle->h_trans = trans2
 do_get_write_access
  jh->b_modified = 0
  jh->b_frozen_data = frozen_buffer
  jh->b_next_transaction = trans2
 jbd2_journal_dirty_metadata
  is_handle_aborted
   is_journal_aborted // return false

           --> jbd2 abort <--

                     while (commit_transaction->t_buffers)
                      if (is_journal_aborted)
                       jbd2_journal_refile_buffer
                        __jbd2_journal_refile_buffer
                         WRITE_ONCE(jh->b_transaction,
						jh->b_next_transaction)
                         WRITE_ONCE(jh->b_next_transaction, NULL)
                         __jbd2_journal_file_buffer(jh, BJ_Reserved)
        J_ASSERT_JH(jh, jh->b_frozen_data == NULL) // assertion failure !

The reproducer (See detail in [Link]) reports:
 ------------[ cut here ]------------
 kernel BUG at fs/jbd2/transaction.c:1629!
 invalid opcode: 0000 [#1] PREEMPT SMP
 CPU: 2 PID: 584 Comm: unlink Tainted: G        W
 5.19.0-rc6-00115-g4a57a8400075-dirty #697
 RIP: 0010:jbd2_journal_dirty_metadata+0x3c5/0x470
 RSP: 0018:ffffc90000be7ce0 EFLAGS: 00010202
 Call Trace:
  <TASK>
  __ext4_handle_dirty_metadata+0xa0/0x290
  ext4_handle_dirty_dirblock+0x10c/0x1d0
  ext4_delete_entry+0x104/0x200
  __ext4_unlink+0x22b/0x360
  ext4_unlink+0x275/0x390
  vfs_unlink+0x20b/0x4c0
  do_unlinkat+0x42f/0x4c0
  __x64_sys_unlink+0x37/0x50
  do_syscall_64+0x35/0x80

After journal aborting, __jbd2_journal_refile_buffer() is executed with
holding @jh->b_state_lock, we can fix it by moving 'is_handle_aborted()'
into the area protected by @jh->b_state_lock.

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


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

	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 4.14.291 with commit 0f61c6dc4b714be9d79cf0782ca02ba01c1b7ac3
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 4.19.256 with commit 6073389db83b903678a0920554fa19f5bdc51c48
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 5.4.211 with commit fa5b65d39332fef7a11ae99cb1f0696012a61527
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 5.10.137 with commit f7161d0da975adc234161cd0641d0e484f5ce375
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 5.15.61 with commit e62f79827784f56499a50ea2e893c98317b5407b
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 5.18.18 with commit 731c1662d838fe954c6759e3ee43229b0d928fe4
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 5.19.2 with commit ddd896792e1718cb84c96f3e618270589b6886dc
	Issue introduced in 2.6.19 with commit 470decc613ab2048b619a01028072d932d9086ee and fixed in 6.0 with commit 4a734f0869f970b8a9b65062ea40b09a5da9dba8

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-50126
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/jbd2/transaction.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/0f61c6dc4b714be9d79cf0782ca02ba01c1b7ac3
	https://git.kernel.org/stable/c/6073389db83b903678a0920554fa19f5bdc51c48
	https://git.kernel.org/stable/c/fa5b65d39332fef7a11ae99cb1f0696012a61527
	https://git.kernel.org/stable/c/f7161d0da975adc234161cd0641d0e484f5ce375
	https://git.kernel.org/stable/c/e62f79827784f56499a50ea2e893c98317b5407b
	https://git.kernel.org/stable/c/731c1662d838fe954c6759e3ee43229b0d928fe4
	https://git.kernel.org/stable/c/ddd896792e1718cb84c96f3e618270589b6886dc
	https://git.kernel.org/stable/c/4a734f0869f970b8a9b65062ea40b09a5da9dba8