linux-cve-announce - CVE-2023-54192: f2fs: fix null pointer panic in tracepoint in __replace_atomic_write

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: <2025123027-CVE-2023-54192-f8f5@gregkh>
Date: Tue, 30 Dec 2025 13:10:00 +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-54192: f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block

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

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

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

f2fs: fix null pointer panic in tracepoint in __replace_atomic_write_block

We got a kernel panic if old_addr is NULL.

https://bugzilla.kernel.org/show_bug.cgi?id=217266

BUG: kernel NULL pointer dereference, address: 0000000000000000
 Call Trace:
  <TASK>
  f2fs_commit_atomic_write+0x619/0x990 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43]
  __f2fs_ioctl+0xd8e/0x4080 [f2fs a1b985b80f5babd6f3ea778384908880812bfa43]
  ? vfs_write+0x2ae/0x3f0
  ? vfs_write+0x2ae/0x3f0
  __x64_sys_ioctl+0x91/0xd0
  do_syscall_64+0x5c/0x90
  entry_SYSCALL_64_after_hwframe+0x72/0xdc
 RIP: 0033:0x7f69095fe53f

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


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

	Issue introduced in 6.1.18 with commit 9ad51915f4b368eef8f4cbd3a0b6367d4504c245 and fixed in 6.1.29 with commit 424f8cdc0ad29e4940be96dcc0b935ba497adeda
	Issue introduced in 6.2.5 with commit f955d66b179679312310d42108c0df1cd0714313 and fixed in 6.2.16 with commit 1424358cd66c49460493293497b54cb72e0213cc
	Issue introduced in 6.3 with commit 2f3a9ae990a7881c9a57a073bb52ebe34fdc3160 and fixed in 6.3.3 with commit e2bbefc1741cb0732c13652be173da02f25611d1
	Issue introduced in 6.3 with commit 2f3a9ae990a7881c9a57a073bb52ebe34fdc3160 and fixed in 6.4 with commit da6ea0b050fa720302b56fbb59307e7c7531a342

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-54192
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/segment.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/424f8cdc0ad29e4940be96dcc0b935ba497adeda
	https://git.kernel.org/stable/c/1424358cd66c49460493293497b54cb72e0213cc
	https://git.kernel.org/stable/c/e2bbefc1741cb0732c13652be173da02f25611d1
	https://git.kernel.org/stable/c/da6ea0b050fa720302b56fbb59307e7c7531a342