CVE-2026-89838: f2fs: limit recovery filename logging to stored length

CVE-2026-89838: f2fs: limit recovery filename logging to stored length

[Greg Kroah-Hartman]

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

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

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

f2fs: limit recovery filename logging to stored length

F2FS stores recovery filenames as a length plus a fixed-size i_name
buffer.  The buffer is not NUL-terminated, but recover_inode() and
recover_dentry() print it with %s.

For a 255-byte filename, recovery logging can read past i_name into the
following raw inode fields.

Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.

The Linux kernel CVE team has assigned CVE-2026-89838 to this issue.


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

	Issue introduced in 3.11 with commit f356fe0cba0e3523e538987916bd2acedd4e6f41 and fixed in 7.2.5 with commit 317d32e1a8deaf1c01c388badc667334c39e62ca
	Issue introduced in 3.11 with commit f356fe0cba0e3523e538987916bd2acedd4e6f41 and fixed in 7.3-rc1 with commit 01027b2fcb74dade59fb833b51023f6593b6a9a2

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-2026-89838
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/recovery.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/317d32e1a8deaf1c01c388badc667334c39e62ca
	https://git.kernel.org/stable/c/01027b2fcb74dade59fb833b51023f6593b6a9a2