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 4552A4BF959 for ; Sun, 18 Oct 2026 15:21:30 +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=1792336891; cv=none; b=MempQ3kQoQrQjT8pvohLaBWZ2kUUiFs9NGts4GTbqU9/1c6M4NfSLSHt3pAfSgUU3NPviXHZGmr6HxIJVkh6T6IMjNaIRJZGCx1zk0S9KjaVPqDBzhNyuXuGgzSnyY1zxtPgJMZnswdlBWTiLAlDRNL0E85GfnRYgVqvsp23D2g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792336891; c=relaxed/simple; bh=BesnbkPiIawY1HSQh8CpE4XKDcSFm8yXlrnnx8JcGX0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=kOVBeXjIWan9d24sIt954siCGsmWTyM7HIjLnoXvi1sF2AF2aMPVrkNf/P8zkTt1j3GkvMGV+9zkRl1UhS2MmMVRwgVh7FOWs7bmfqMW2PO1Y3XWFELPcGQyEjhOcT4ujU84v9AgdlVxwKXfsKKmzmWVWKB9PVvaKDH5luiyFu4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=q7s3hqlg; 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="q7s3hqlg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6599B1F000C4; Sun, 18 Oct 2026 15:21:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792336890; bh=AYwbpjfw/y7Wqx1ZXGHI/5aPLZGn+T/SprAtFlTbJqQ=; h=From:To:Cc:Subject:Date:Reply-To; b=q7s3hqlgsDKZvyuDSzSBHiibWOVQj7kHt3DBWY4HLvx8rfgoL7gMQZgQhOVq39NTN NkBqebB2SZA/XmeSigMJhav3kfgE/eJ/bwOynDxRLl86cDedxZPtZBF1mAMNG5+mkd eu0twkwkFKqt5J4R2zjJnNtbfwH2KlJ+4yBwQkE0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98445: xfs: don't let memory failures leak blocks and kill repairs Date: Sun, 18 Oct 2026 17:15:09 +0200 Message-ID: <2026101807-CVE-2026-98445-afa2@gregkh> X-Mailer: git-send-email 2.56.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=2777; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=MiuyMjJ9gWDSTrfWOcHphZF3XMnnsNLKZz610f9vBcE=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXHlWH//vfPOE5m3W8gUJUEtu1k/InAkUyUnld2PQfh h89Z3S5I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZiupthwb7Oxmc3jM/Y5weE vfnKX/I09e7idQyzWeKnqgnELu7ds27LX2+bnP9Gz85lAAA= 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: don't let memory failures leak blocks and kill repairs LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down. However, the new btree space reservation object isn't that big (~48 bytes). Let's just do a NOFAIL allocation and the problem goes away. The Linux kernel CVE team has assigned CVE-2026-98445 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 6.12.113 with commit 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 6.18.56 with commit b15c79fca28060fd9c7e77f2c3ebc4ba023974e8 Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 7.2.9 with commit 0e0d3372a84029da1768c7a4c4601484af5b58a2 Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 7.3-rc5 with commit ab1c416d2377cdc16123ef521aac4da1c468c3d4 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-98445 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/scrub/newbt.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/3380151cf0ce8ad0c1d356fed51e4b69e1d28e50 https://git.kernel.org/stable/c/b15c79fca28060fd9c7e77f2c3ebc4ba023974e8 https://git.kernel.org/stable/c/0e0d3372a84029da1768c7a4c4601484af5b58a2 https://git.kernel.org/stable/c/ab1c416d2377cdc16123ef521aac4da1c468c3d4