From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 34A192135AA for ; Wed, 26 Feb 2025 02:13:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536007; cv=none; b=FjPvuBRsEbaFWFHN9NgJgMv0OMLuZYmQ/sdE03HqTliKcaDaQztkUmj36yro+e+x5RT54heaR2YY6e8RHY1bl+Y42EIBru6WIS99G2Ravji7WImN3NgjYhABBmtrKruKte0xP9/ZeS8gXZiO6thiOs6gd2p7ad+dvcM2JvKH0XU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536007; c=relaxed/simple; bh=tKFPBgGXaCyXVbsZeAL4og1BuWHbGaTu9aXYb7com8g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=jBuGXU6HBcYNMFVGR8KIN+Ql2DUHDfRMkHml77MMk6aTWvXL9fMVxpCRS0jOUZvmju8wDrmsmcqtlc2oL/jG2za8DRNaJkN2pjsjlTNcS1kQDxtYp4JkzH0ClIeFeKLTjYRepEB60ZYQZvUK4i8IstB7igL5EAJy6sOUbctjjgY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=o/TSbzSk; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="o/TSbzSk" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 09020C4CEDD; Wed, 26 Feb 2025 02:13:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536007; bh=tKFPBgGXaCyXVbsZeAL4og1BuWHbGaTu9aXYb7com8g=; h=From:To:Cc:Subject:Date:Reply-to:From; b=o/TSbzSklS3xrZdc8S1IUaF6oJy/Okagp0SL0duKeMZlZ4+HDrhlHpgudkTjzFihj zfarlDN0o2pwJiiO/W8vQaMRhY1SQjHgzA38mibE+QNm6VrEKm5SBGqw/ZJFTSbi7Z nfaOKuNCuZ5ig/U2x0lwIQKtJ/W8QcYtO9zh4aOs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49364: f2fs: fix to clear dirty inode in f2fs_evict_inode() Date: Wed, 26 Feb 2025 03:10:38 +0100 Message-ID: <2025022644-CVE-2022-49364-29dc@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3296; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=tKFPBgGXaCyXVbsZeAL4og1BuWHbGaTu9aXYb7com8g=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7yl8yuxk+4fKYv+FnGcsFv5VnG78lph7Yc5gxSUNr3 YGutu4pHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARgf0MC/pm+VXP273/fGUo Q/iTpZ97tvza0MywYJGwhN8VFY0yp/hcs/Oe555eyuvQBgA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to clear dirty inode in f2fs_evict_inode() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215904 The kernel message is shown below: kernel BUG at fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 The root cause is: inode node and dnode node share the same nid, so during f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty for inode and setting SBI_NEED_FSCK flag in filesystem. output from dump.f2fs: [print_node_info: 354] Node ID [0xf:15] is inode i_nid[0] [0x f : 15] The Linux kernel CVE team has assigned CVE-2022-49364 to this issue. Affected and fixed versions =========================== Fixed in 5.4.198 with commit 54c116615c99e22aa08aa950757ed726e2f60821 Fixed in 5.10.121 with commit ccd58045beb997544b94558a9156be4742628491 Fixed in 5.15.46 with commit c9196d21359be8c7ee231029d13682273925fd00 Fixed in 5.17.14 with commit 03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 Fixed in 5.18.3 with commit c469953917b319d415fd621b9e5d0ea5203565cd Fixed in 5.19 with commit f2db71053dc0409fae785096ad19cce4c8a95af7 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-49364 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/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/54c116615c99e22aa08aa950757ed726e2f60821 https://git.kernel.org/stable/c/ccd58045beb997544b94558a9156be4742628491 https://git.kernel.org/stable/c/c9196d21359be8c7ee231029d13682273925fd00 https://git.kernel.org/stable/c/03c9373b15fa1c245ec99b2b5e7ba209eae4ef42 https://git.kernel.org/stable/c/c469953917b319d415fd621b9e5d0ea5203565cd https://git.kernel.org/stable/c/f2db71053dc0409fae785096ad19cce4c8a95af7