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 726743A873A for ; Sun, 19 Jul 2026 15:46:45 +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=1784476006; cv=none; b=h709fiUQ0n/AftI//iyWYTlf6sS8aoIl7IlDi60uBpqfpKafR1RVQrUcOFxrBrc04rGvtxjvR/sTasPFwIKeIDuEskgXY/aBgaW1iwLdGq2CmHnJkCldI1L0yImc9CtNaFBt5mymRosohahMfogNa1nAH8Tds18Eevn/5zFo+mU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784476006; c=relaxed/simple; bh=SQQ/1EuPTQxE/gI9Hco3hfVeeNnQItiNJqPEgR3yGeU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FGEV/iFcdkzh9NG6QrcNsHKayXn0dibJ2LrIrSCPpxSodaf80aeFpYSR2GCh6Hs/NXYuhSfz5btEWAJqHwAdLUfFljb74kkLIl7GGCdNI0+IW9sFqCr7PxXEcCST6IQACvrM1Uy5x8ZutTsBflaRMiUzz6Ipr7bi1PWfA6re+Gg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=jqM0zLhb; 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="jqM0zLhb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C3D911F000E9; Sun, 19 Jul 2026 15:46:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784476005; bh=VVtDd0W3bYKWNYj1axjyBGwab3aIHuXMDkWM642wU/s=; h=From:To:Cc:Subject:Date:Reply-To; b=jqM0zLhb8COWBFUsR+grLt1uItY13N78JW/k6F+uWCqRwHSNGee7uSdJ2Fq158Ft3 CeJ5ekKkoUZbm0OZiPH+BsHopfkEuYNBQFNunw2nMqh522uk+Xkb+2bplQeypYekrs 8t14Fkod++DD6iAD6+J02beIyD2OstXqpsh86CYA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64160: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point Date: Sun, 19 Jul 2026 17:40:22 +0200 Message-ID: <2026071933-CVE-2026-64160-8bee@gregkh> X-Mailer: git-send-email 2.55.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=2534; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YIXZsGK5CkFvmmmw0pkOMLgGSLlT/TziegH6FwzRZhk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx7yu91wUbT4nwFv68pvb2keAPAu9+/b56okbg1MX98 9elv55zrCOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAmYprHsGCvi7hM/cVrMape J17s2n33jsyLP3MYFpwRefb+rGtOs9NS5jSnL6wbxTJD3gAA 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: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point Fix potential tearing in using ->remote_i_size and ->zero_point by copying i_size_read() and i_size_write() and using the same seqcount as for i_size. We need to make sure that netfslib and the filesystems that use it always hold i_lock whilst updating any of the sizes to prevent i_size_seqcount from getting corrupted. The Linux kernel CVE team has assigned CVE-2026-64160 to this issue. Affected and fixed versions =========================== Issue introduced in 5.18 with commit 4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 and fixed in 7.0.11 with commit 55970f238d495517edc961d55c44c772594d0969 Issue introduced in 5.18 with commit 4058f742105ecfcbdf99e1139e6c1f74fb8e6db9 and fixed in 7.1 with commit 2c8f4742bb76117d735f92a3932d85239b16c494 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-64160 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/9p/v9fs_vfs.h fs/9p/vfs_inode.c fs/9p/vfs_inode_dotl.c fs/afs/file.c fs/afs/inode.c fs/afs/internal.h fs/afs/write.c fs/netfs/buffered_read.c fs/netfs/buffered_write.c fs/netfs/direct_write.c fs/netfs/misc.c fs/netfs/write_collect.c fs/smb/client/cifsfs.c fs/smb/client/cifssmb.c fs/smb/client/file.c fs/smb/client/inode.c fs/smb/client/readdir.c fs/smb/client/smb2ops.c fs/smb/client/smb2pdu.c include/linux/netfs.h 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/55970f238d495517edc961d55c44c772594d0969 https://git.kernel.org/stable/c/2c8f4742bb76117d735f92a3932d85239b16c494