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=1795154280; b=QZEAVOfJ+3Tc/srpjmJ5ilyxL+4cRGYTvYW2EpZB5a6hzYprbElJHF+4KNDS5t3RR4u3 sQjJa2AqmOgb2s+tZ78EFJx1HMUkgcxBk7g06cU39ny+9KNvLFrxth9Jf89Y2Pgc60dso GMfDps6C8NhDDy7D0Pf03mK14xDr2ucTvuDx6oTvAElXEYA3spSUHiiPSVChzBfbe8Rjx w9IU//cJ1c5ZRt/D2bX1xNujz+rROEGqE/bW4yTQlbp055IatmbQ288eep0RjBRq60iFK E0s81dUjT20SXHq2oyzrTeyCbx3Hk/7RtLddz+l88Z0Xx8Gsf9Q65Uo3kovvsn9PEcg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154280; 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=HTve6g61SeFAm5PGIMeOyVSquXePjPe5UNdun1rP2L0=; b=tUerRFwhxQAT1CdaVLcrwsrpf69Vd1jml8/Q9apDO0gQzYt1TRjlkY8zeDcEtvU/o/oR oecNBxQfRoyDEpUOA7dopTnaBd9cZIyMbmJCtK+wZK1BwE/1raa7cDXGeh1vsDFetlhpG KMECapTJWqnA8lLZTi9GgeHcvPNrX/OFp0xgN6yl/jJ42TPOrlfa/meQtT46f4EaprtrZ ulFelwVBfUwVzODQN274fTuT3CmFSvBJM1gfLzese9LsO42rU7qPSQCEIAijwBSy2hIvN sCFa1Q8a/siRBuYVyaa7cdwUpwmflIrrhlhu9xDQEe5/L+zuhsSrIUPTA/3axJU1EUQ== 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=a5jUyMVg; 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 ECA6A606A332 for ; Fri, 20 Nov 2026 05:57:59 +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=a5jUyMVg Received: by smtp.kernel.org (Postfix) with ESMTPSA id 491421F000C4; Fri, 20 Nov 2026 05:57:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154279; bh=HTve6g61SeFAm5PGIMeOyVSquXePjPe5UNdun1rP2L0=; h=From:To:Cc:Subject:Date:Reply-To; b=a5jUyMVgGtWgtarQDy74O5C9DL38JAh7ikj3X71Cz63SLbwWkYroGiMnh5Nbmp8WU Hp1pgj6ykgW8DCK9MuyJakgx66/4+W8xRNzlwuZCoEzs8hUtZVL+dJIQvu5xF/9inl BOaxGcfSVcZjRMp6aUwKIXzhwbXE7MHDL5GcsFL4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99689: xfs: fix temporary cursor leak in btree shift corruption paths Date: Fri, 20 Nov 2026 06:51:15 +0100 Message-ID: <2026112057-CVE-2026-99689-bf59@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=2731; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=TAQscNLzw9MvsFtdiAioFeI7PlvDLu9jqQ0b6+zD4CY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/77f9cZFrEn62PUslTdhwR/a8Dxk/0nt+bQs0Ck0ym 3thtYpQRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzE4TLDgi62NfIzF6TovVp6 +Gf7xdz7bifPvGSY7/a2xHBfyg++E+tbjgT4S4ucfXF0IwA= 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: fix temporary cursor leak in btree shift corruption paths In xfs_btree_lshift and xfs_btree_rshift, when XFS_IS_CORRUPT detects an invalid firstrec/lastrec result after xfs_btree_dup_cursor has successfully allocated a temporary cursor, the error path jumps to error0 which returns without freeing tcur. This leaks the cursor memory, the xfs_group reference, and the per-level buffer references held by the duplicated cursor. Jump to error1 instead, which calls xfs_btree_del_cursor(tcur, XFS_BTREE_ERROR) to properly release all resources. The Linux kernel CVE team has assigned CVE-2026-99689 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 6.12.118 with commit 3f52eb7dd4a584c60f1b190b18fa4958b5fbef65 Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 6.18.64 with commit fa4189dbbd9487de3ef9437572a29c71c5521fe5 Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 7.3.5 with commit 845ef1a6277f8b8bdf6479c6f561c16e5d5f56e2 Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 7.4-rc2 with commit 2bbca049deeb1699cafd966cb2793fee576ee409 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-99689 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/libxfs/xfs_btree.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/3f52eb7dd4a584c60f1b190b18fa4958b5fbef65 https://git.kernel.org/stable/c/fa4189dbbd9487de3ef9437572a29c71c5521fe5 https://git.kernel.org/stable/c/845ef1a6277f8b8bdf6479c6f561c16e5d5f56e2 https://git.kernel.org/stable/c/2bbca049deeb1699cafd966cb2793fee576ee409