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=1795154354; b=Pjm2/uhgIVkLw5x2X7qaQvFLoVuhzRxCdDRqdJtk1t6ztTXDiWPFnf9lrCUge+mv7g2F Mi2kdo6KTtv64IENREB68fci2ABqeWOGGqq2VMm8De2Yn93k+6Q96Kz6GjKkDevzS4JEv 4zH75pQcEs2v9y6Im7wSOpXycaDCBKtZce/6+tw7LZ19IC6dPdjF9oKbK0aYg/T/nbjoH Weokj/IR0Khz4gtljXuZ0vgDBGZt9BUNc6tNs6vRDWgT6WnkftXopKYEBJJHdJDxI8WkC CVqB0yV4Vr+3xPBOq2PkAfE+p4mrHMRU3MrLVK5798Kg8XtdgVcg1rLBHGJwSkBlX8A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154354; 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=dA0LvJQl76YmNHHDAsRQyr92ocHEKCbuAltqGK73DCU=; b=I1U5dfoCO+Unbm5c7ohKnHlUiDCRD+hBGBWtM4HcNzU1ZUkfFV8ljFcMZsfiA32uWXCd nB1+cK8vYXLRRQf3eiClDS7LbzcTqlnoDb75U7hCCnwHD/JnRA9AwJvoAdUdGx9vEbK2Z i0mIxIZ+creSk8iHQF8PMIpBadE8IdO0QBj9izjboxTo+EXwwi8kMO1Cl/WoTU72ZtIZ5 08qNrHyxPdMeDcrD7lPBm4QQElJ6Er1dXsvusSOF2L9x7Tmzq0viYjFoEC1r+6Dm9Lyvr CI/Lziw2rRku1geN6ovRHA3O+b7a23mox6JAlHS9h4Y3/NBxvvVettLMmdrIb7b94tg== 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=sHh0H0KA; 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 99728606A334 for ; Fri, 20 Nov 2026 05:59:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=sHh0H0KA Received: by smtp.kernel.org (Postfix) with ESMTPSA id EA98B1F000C4; Fri, 20 Nov 2026 05:59:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154354; bh=dA0LvJQl76YmNHHDAsRQyr92ocHEKCbuAltqGK73DCU=; h=From:To:Cc:Subject:Date:Reply-To; b=sHh0H0KADerjIZ7UVX2uuGShnvPoLsr6DBN3e/EK5DkfApxJYGavA8mmpqDCEcEI1 xuaYi12ZrjDjiZpYDuRswQnJGVIe24lb4kG1zSYna0lbJSxy0MmbXnNqFPQlaZfkEm 1M495oPlSrmSYQUXIDTffeqskI1105TusngURwqQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99677: xfs: clamp the pNFS layout range to the maximum file size Date: Fri, 20 Nov 2026 06:51:03 +0100 Message-ID: <2026112053-CVE-2026-99677-e0e9@gregkh> X-Mailer: git-send-email 2.56.1 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=2676; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=aIkvHJGhDMpvTVw3QXOKsNStsMSynPB+zMRajMolMfQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7zfa55tI7grVEpxq56+Xlbx0yfkntTanPrl82J/Nr rMyNzC5I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACby4AfDfIeiG9eZVPYFFjrM dhV9M9mn9MNCDYb5Va/kL+esCUjQtH5RwTjzjPq7H9unAgA= 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: xfs: clamp the pNFS layout range to the maximum file size xfs_fs_map_blocks() lets two bad layout ranges through. An offset of 2^63 or more is negative and passes "offset > limit". A length above the limit, such as NFS4_UINT64_MAX, wraps "offset > limit - length" and stays unclamped. With NFS4_UINT64_MAX, a read layout is built from an uninitialized mapping. Reject a negative offset and one at the limit, and clamp the length. This needs "xfs: cap the block count of xfs_iomap_write_direct() at one extent". The Linux kernel CVE team has assigned CVE-2026-99677 to this issue. Affected and fixed versions =========================== Issue introduced in 4.0 with commit 527851124d10f9c50b1c578e0a56fcd49922422d and fixed in 6.12.118 with commit df8632f36be4693677c18966319ae546b4341061 Issue introduced in 4.0 with commit 527851124d10f9c50b1c578e0a56fcd49922422d and fixed in 6.18.64 with commit 8e0cea93da8755cfebe9a0ea7e2b37e68d59118d Issue introduced in 4.0 with commit 527851124d10f9c50b1c578e0a56fcd49922422d and fixed in 7.3.5 with commit e8c7a13a7b63542753ab3c6c55b142b09d207c78 Issue introduced in 4.0 with commit 527851124d10f9c50b1c578e0a56fcd49922422d and fixed in 7.4-rc2 with commit 29f3c1be4e554c9dbc66e13333034e0947477cb6 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-99677 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/xfs/xfs_pnfs.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/df8632f36be4693677c18966319ae546b4341061 https://git.kernel.org/stable/c/8e0cea93da8755cfebe9a0ea7e2b37e68d59118d https://git.kernel.org/stable/c/e8c7a13a7b63542753ab3c6c55b142b09d207c78 https://git.kernel.org/stable/c/29f3c1be4e554c9dbc66e13333034e0947477cb6