linux-cve-announce - CVE-2022-49361: f2fs: fix to do sanity check for inline inode

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: <2025022644-CVE-2022-49361-40d7@gregkh>
Date: Wed, 26 Feb 2025 03:10:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49361: f2fs: fix to do sanity check for inline inode

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

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

f2fs: fix to do sanity check for inline inode

Yanming reported a kernel bug in Bugzilla kernel [1], which can be
reproduced. The bug message is:

The kernel message is shown below:

kernel BUG at fs/inode.c:611!
Call Trace:
 evict+0x282/0x4e0
 __dentry_kill+0x2b2/0x4d0
 dput+0x2dd/0x720
 do_renameat2+0x596/0x970
 __x64_sys_rename+0x78/0x90
 do_syscall_64+0x3b/0x90

[1] https://bugzilla.kernel.org/show_bug.cgi?id=215895

The bug is due to fuzzed inode has both inline_data and encrypted flags.
During f2fs_evict_inode(), as the inode was deleted by rename(), it
will cause inline data conversion due to conflicting flags. The page
cache will be polluted and the panic will be triggered in clear_inode().

Try fixing the bug by doing more sanity checks for inline data inode in
sanity_check_inode().

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


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

	Fixed in 5.10.121 with commit efdefbe8b7564602ab446474788225a1f2a323b5
	Fixed in 5.15.46 with commit 7cfe2d43becaf76e562b9617d2c2d9b445f86761
	Fixed in 5.17.14 with commit 11c1cd032df85df3c096a57a7f27d57819956e4a
	Fixed in 5.18.3 with commit 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
	Fixed in 5.19 with commit 677a82b44ebf263d4f9a0cfbd576a6ade797a07b

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-49361
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/f2fs.h
	fs/f2fs/inline.c
	fs/f2fs/inode.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/efdefbe8b7564602ab446474788225a1f2a323b5
	https://git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761
	https://git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a
	https://git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
	https://git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b