CVE-2022-49361

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 following products are affected by CVE-2022-49361 vulnerability.

Here, you will find a curated list of external links that provide in-depth information to CVE-2022-49361.

URL	Resource
https://git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a
https://git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8
https://git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b
https://git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761
https://git.kernel.org/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5
https://lore.kernel.org/linux-cve-announce/2025022644-CVE-2022-49361-40d7@gregkh/T
https://nvd.nist.gov/vuln/detail/CVE-2022-49361
https://www.cve.org/CVERecord?id=CVE-2022-49361