From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 09C3B314B9A for ; Wed, 24 Jun 2026 16:35:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318927; cv=none; b=cXYNk1V8Cm9BTPErCRr6KiATEYs3c5HsmbRuAJBH/Wcqw2VS8ZurNvQEGavzXSWfszSrdDPclytAaBk8p88rFcJPALwMugR6w2CeMiowdDS/QWi2FlJJAOEnZhmdA/hzW+97CQhbKHqdI8UB4KBOHa6tTrw3Ewv1SvcD8yD477k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318927; c=relaxed/simple; bh=GPBZmI9lVrXw9OvLcRM7euqa6JxE+oJ+Za1mm71SS94=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=a9wbpmdQcOIA/qkmYaq7gAoePWm4CIXXFN2Bz0rjo4i+NnU6HT0O6EsXNZyHSFxqjJPFeLcG2ENOAo0yJSiQrBJwW/VvKkBoIRe9TyOgWQGQrXvpk0JGp0mED1t5R1mg5cN9KwwP0+5r68O5HOHHCKY8mSchvLGYk+oKb6e3Q94= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=wyDXorPP; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="wyDXorPP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4FD9B1F000E9; Wed, 24 Jun 2026 16:35:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1782318925; bh=i2M9tR+W/8VuHMKspe+Z1trKBI48p7PR6FHAsclhUHE=; h=From:To:Cc:Subject:Date:Reply-To; b=wyDXorPP92XzsAQiegbV3lp6ymvOEqLhtKKlK+si2WtCYkrdtKO38PEimEZqAUYto 2D6Huy0iQmbMfgQyrsbbpZJOFLoNvsqnqOBk3DRlvi2lpKxj0xgVPXLJf7CHJ4HI9C 8xCMrrS3OCY7UVnDgmvoCKMx9GTdlCGH+B/LJ+hU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-53017: f2fs: fix data loss caused by incorrect use of nat_entry flag Date: Wed, 24 Jun 2026 17:30:41 +0100 Message-ID: <2026062451-CVE-2026-53017-645d@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3197; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=DbGCuOeWTUNsrfKju/1XDZA3VyBxvb8lCseLFMMalIU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFk2rP83CLaqfboaqfx7qlbWU2E78Xnn1i4IUrkTaxD8/ FBY7ZWqjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiIjAjDHM6KhoXKti93MDw2 rX2yYdW3lJ2f1RnmGcl5HP92ykh844RAq6s7gpaoTSoRBgA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: f2fs: fix data loss caused by incorrect use of nat_entry flag Data loss can occur when fsync is performed on a newly created file (before any checkpoint has been written) concurrently with a checkpoint operation. The scenario is as follows: create & write & fsync 'file A' write checkpoint - f2fs_do_sync_file // inline inode - f2fs_write_inode // inode folio is dirty - f2fs_write_checkpoint - f2fs_flush_merged_writes - f2fs_sync_node_pages - f2fs_flush_nat_entries - f2fs_fsync_node_pages // no dirty node - f2fs_need_inode_block_update // return false SPO and lost 'file A' f2fs_flush_nat_entries() sets the IS_CHECKPOINTED and HAS_LAST_FSYNC flags for the nat_entry, but this does not mean that the checkpoint has actually completed successfully. However, f2fs_need_inode_block_update() checks these flags and incorrectly assumes that the checkpoint has finished. The root cause is that the semantics of IS_CHECKPOINTED and HAS_LAST_FSYNC are only guaranteed after the checkpoint write fully completes. This patch modifies f2fs_need_inode_block_update() to acquire the sbi->node_write lock before reading the nat_entry flags, ensuring that once IS_CHECKPOINTED and HAS_LAST_FSYNC are observed to be set, the checkpoint operation has already completed. The Linux kernel CVE team has assigned CVE-2026-53017 to this issue. Affected and fixed versions =========================== Issue introduced in 3.8 with commit e05df3b115e7308afbca652769b54e4549fcc723 and fixed in 7.0.10 with commit 20cedb4d9f6b230d0ee469690b8f868f06a07c29 Issue introduced in 3.8 with commit e05df3b115e7308afbca652769b54e4549fcc723 and fixed in 7.1 with commit 238e14eb7226f883b72caccd2d37bf5707df066b 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-53017 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/node.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/20cedb4d9f6b230d0ee469690b8f868f06a07c29 https://git.kernel.org/stable/c/238e14eb7226f883b72caccd2d37bf5707df066b