[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122417-CVE-2023-54124-d6ac@gregkh>
Date: Wed, 24 Dec 2025 14:07:21 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54124: f2fs: fix to drop all dirty pages during umount() if cp_error is set
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to drop all dirty pages during umount() if cp_error is set
xfstest generic/361 reports a bug as below:
f2fs_bug_on(sbi, sbi->fsync_node_num);
kernel BUG at fs/f2fs/super.c:1627!
RIP: 0010:f2fs_put_super+0x3a8/0x3b0
Call Trace:
generic_shutdown_super+0x8c/0x1b0
kill_block_super+0x2b/0x60
kill_f2fs_super+0x87/0x110
deactivate_locked_super+0x39/0x80
deactivate_super+0x46/0x50
cleanup_mnt+0x109/0x170
__cleanup_mnt+0x16/0x20
task_work_run+0x65/0xa0
exit_to_user_mode_prepare+0x175/0x190
syscall_exit_to_user_mode+0x25/0x50
do_syscall_64+0x4c/0x90
entry_SYSCALL_64_after_hwframe+0x72/0xdc
During umount(), if cp_error is set, f2fs_wait_on_all_pages() should
not stop waiting all F2FS_WB_CP_DATA pages to be writebacked, otherwise,
fsync_node_num can be non-zero after f2fs_wait_on_all_pages() causing
this bug.
In this case, to avoid deadloop in f2fs_wait_on_all_pages(), it needs
to drop all dirty pages rather than redirtying them.
The Linux kernel CVE team has assigned CVE-2023-54124 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.284 with commit 92575f05a32dafb16348bfa5e62478118a9be069
Fixed in 5.4.244 with commit 4ceedc2f8bdffb82e40b7d1bb912304f8e157cb1
Fixed in 5.10.181 with commit ad87bd313f70b51e48019d5ce2d02d73152356b3
Fixed in 5.15.113 with commit d8f4ad5f3979dbd8e6251259562f12472717883a
Fixed in 6.1.30 with commit 7741ddc882a0c806a6508ba8203c55a779db7a21
Fixed in 6.3.4 with commit 82c3d6e9db41cbd3af1d4f90bdb441740b5fad10
Fixed in 6.4 with commit c9b3649a934d131151111354bcbb638076f03a30
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-54124
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/f2fs/checkpoint.c
fs/f2fs/data.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/92575f05a32dafb16348bfa5e62478118a9be069
https://git.kernel.org/stable/c/4ceedc2f8bdffb82e40b7d1bb912304f8e157cb1
https://git.kernel.org/stable/c/ad87bd313f70b51e48019d5ce2d02d73152356b3
https://git.kernel.org/stable/c/d8f4ad5f3979dbd8e6251259562f12472717883a
https://git.kernel.org/stable/c/7741ddc882a0c806a6508ba8203c55a779db7a21
https://git.kernel.org/stable/c/82c3d6e9db41cbd3af1d4f90bdb441740b5fad10
https://git.kernel.org/stable/c/c9b3649a934d131151111354bcbb638076f03a30
Powered by blists - more mailing lists