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 293FC215F51 for ; Wed, 26 Feb 2025 02:13:25 +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=1740536005; cv=none; b=N8NIthMNp2fb7T2Uorn22mPagd+vRrIj8Dsg14Zu9IzJg2H4Dya/c1D66w3wMpHjahqVofpeyms42S/F7UyL0UxHeB30umqWkURmbZBE4Haz/qxnEdFbWuYiU6un+OKafXlV9qnugInU0hwy9w5lrg9rckLbA6tKqF2rMkihkUI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536005; c=relaxed/simple; bh=ZLLaHKQI5HC1OIcei2b3iOh5nRWHey0eSuMiN3nbowA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FaOeZG+d+92d1dEUsjB1c93fs8LvNzPeCCviL1l5K0qU0AcC2JcQ/JBFjH+QVufTyviB2Euv6Ky6CoHBSdUeMpuTRU26OT29WHybGSkfKHv1XGZvjOmqJkKMrwvgYeMqsUz2W3TLSOZ2Rg/IQlOV+bO7btJewVaWv00CldwLw64= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=I1BbrOav; 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="I1BbrOav" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E6971C4CEDD; Wed, 26 Feb 2025 02:13:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536005; bh=ZLLaHKQI5HC1OIcei2b3iOh5nRWHey0eSuMiN3nbowA=; h=From:To:Cc:Subject:Date:Reply-to:From; b=I1BbrOav2oSiaPm3kxYGPaKjR1QyD1FXbP9gspo20DbV8ZOYbQCb1+jsAZ7IZGtDv +YHgQddHEZrozKyt66neIRpwtlLRktww8FYtYrEu/YugSpMeXX5uhD1qjW3lhC0ZV0 nzp0Cs1kJCyDqWpVqRyah2iONkNf4wbv7PjjJAtA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49361: f2fs: fix to do sanity check for inline inode Date: Wed, 26 Feb 2025 03:10:35 +0100 Message-ID: <2025022644-CVE-2022-49361-40d7@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=2835; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ZLLaHKQI5HC1OIcei2b3iOh5nRWHey0eSuMiN3nbowA=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7yl8U2W881d2r0t7gdqA0b5v1jYBHxw9UB1g+Xnymz Ft4ukFBRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykz5RhfrKZg9LRmW/6jx2d 7ZSmIVeyVuOZJcP8jE/vZiseeu16+4tTMF+tkXB9/y8OAA== 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 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