From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793187393; b=hPF9YX1RPc9XDOPfEf8sqdI62tiHKBJmSS4vOXPGVKvISfaLan9gtBBcxaqHht5u2Onn KdZ6P3fzK58xQPCdLhQ73MfS0+mMurLMzUfEHng0Px25Tvm9Eqoe7IAs8cpnFDIzVFZ3E I/XZEH6R1nw+R1TB9xNH8gRtSY0hgyavNMhVeWJ9CEaob8oLKcHBf8oIWa3z4ZC3gcBJH IMHOygQVBsCxQV7dCQrxGK3A6BGJeT4b71LirKhbuzUcB61MXbsspN13i8G+dcsCVTMsh P7ItTxoAc4fdvteyJ6svJA5VmGX5eEG4lCfBBSPJOUOD3kRln1VcJhiihZcPgWeyyYg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793187393; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=QxX9U43cV4PsI6yLbvqnZNV2cW+8rW5FfV7JYhIJCmk=; b=ZASZYSvq4mUR631mHb7TPrlf0+B6cGalybcMaOv5MmDOBhDPDMa1Ey6mVrRgKWg9ojN/ nMVbPTlsUJTZykodqSWXCPh19h/jnSQbjxbvKswVqVPHQjRiISI6eYzdChJRe1uHBaocq D41M7t79+Cwzp+yiEqq+3w5MoJ2a5F/YIDovfS/+YjvoqU3UouVXdHzmVfWpEEk5EHcW+ TGBIqDolXTvXTQCdMyBVMaSZfZaHsx3LlAHocErX6JgaKRTQSWYWgdinUQrH04JsQ4y8x nhEziHGhnFtM4CIIqw6DNIXbqgGz8ps2u0A8qjlILKNTmA1pykA8g/vaHIv3ErR2xlg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=cGiGJ73p; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CB2CD606A323 for ; Wed, 28 Oct 2026 11:36:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=cGiGJ73p Received: by smtp.kernel.org (Postfix) with ESMTPSA id A3EEE1F01829; Wed, 28 Oct 2026 11:36:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793187392; bh=QxX9U43cV4PsI6yLbvqnZNV2cW+8rW5FfV7JYhIJCmk=; h=From:To:Cc:Subject:Date:Reply-To; b=cGiGJ73p5Xiihk8j9077cKWvzDG5pl3sbPMphXeVHdOKlaHa5pkXAK4ne3Mz1Y3H+ 7suDHTnF16o9aIJ7P/yjUNguepO/Jel4zxyLviXB2nEmdFXryk4cGDdjxVJ6y34sHv tgikqBFslPRf6UPy1dIa44ymejCkS5yDujzYEedI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99102: ntfs: take invalidate_lock in ntfs_setattr_size() Date: Wed, 28 Oct 2026 11:34:49 +0100 Message-ID: <2026102852-CVE-2026-99102-c4fa@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2370; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=mD+JzSwYACahspR+XLfZpqZ8KFD8sUJrikhZQoNZMuo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkPz585GnQivZNvmS730rV9rZ8NDibwdYeqrtKdfGSZ2 NuuLh6zjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZgIrxnDfN+7YlzLjs5JCBV+ t5lPZsLSiXMnZzPMT/36qmxyOU/htL/fzRRmVR7qL1nMDAA= 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: ntfs: take invalidate_lock in ntfs_setattr_size() ntfs_setattr_size() updates i_size and resizes the on-disk attribute without holding mapping->invalidate_lock. Page faults take the lock shared, so a fault racing the resize can resolve a VCN against the transient runlist state of ntfs_non_resident_attr_expand() and fail with a spurious SIGBUS, and can interleave with the size-change epilogue (truncate_pagecache(), i_size_write(), pagecache_isize_extended()). Take invalidate_lock exclusively around the whole resize after inode_dio_wait(), matching the fallocate path and other filesystems such as xfs, which wraps truncate in its mmaplock (= invalidate_lock). The Linux kernel CVE team has assigned CVE-2026-99102 to this issue. Affected and fixed versions =========================== Issue introduced in 7.1 with commit 9c87959601e80b39a45250e362e6ddfec17cb0fa and fixed in 7.2.13 with commit f0b0738ba95731eeafd11352c74f8b48951f67dc Issue introduced in 7.1 with commit 9c87959601e80b39a45250e362e6ddfec17cb0fa and fixed in 7.3 with commit 9cc5761b8f28f9cef72061094eb5e37e2cd44d97 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-99102 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/ntfs/file.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/f0b0738ba95731eeafd11352c74f8b48951f67dc https://git.kernel.org/stable/c/9cc5761b8f28f9cef72061094eb5e37e2cd44d97