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=1792759456; b=OM0xzVbj3S0PVxtFeV3ubpq9MjUbZ8y7ZD/kFcETrDSWXEi+bFjaA7qCpM/eioA+b4aT d5ggw7Sfd2t61M7jAriUIouqdOpvUkpPKbcoGJnWl8ih60NZBTxBndbcXrKU+5vTm0PpI rtGJ+WaLZnkiwj2aURqA7JfuzAkxleygd6Nm+JsuZYjW/r4AYnkalHMpDb6yLLGeU6wLh NtgCUC8nWhN0cD64FKU7THY6arlqc7r2pn6lizZxs+yCU3OeTghUv4usm13dJygxGjXu2 BlIvesv65iQmn7Q2NaFiB2viE014mKRojZnnbS8ZtKPKtKmTt6lxWVsoBHAdwulN+fA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792759456; 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=CGJi4KMy/jfdouKEMxN7bpFIUcIBYlLDGvseKjCuhfc=; b=Pzohab8CKTsxYi1CBq7a3s7yD3ZL7424HPY0umw7bPJLeHDD5jzm+2wbn/AQ9Me1py3x EVts0VpE2vUm1oDHqT7PiG5xkX3Sw394DvWue7buO599aQp2VJkntA8BqVL6Gt/z6vZFC ADmB5xalUr0eo2WI/U5p3DBPnFCviSkrW2AogcnXILDpZwfl1kDLoDVxSP/jPigiurafH Y//7Uqqk/ipl7Bm71EDB7gXGv0VoaPyS6iXQylPigCrTedr8gI6Jtucd2H0K5H9TIUbLF TbFaB8eb7TabMqH2rUKPg+Z7krD8OgBUXpQAD3B026X2P+imdhtfjn4Xto2qE+qSO+A== 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="UrlaC/rJ"; 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 A05C2606A31D for ; Fri, 23 Oct 2026 12:44:16 +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=UrlaC/rJ Received: by smtp.kernel.org (Postfix) with ESMTPSA id C333E1F01825; Fri, 23 Oct 2026 12:44:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792759456; bh=CGJi4KMy/jfdouKEMxN7bpFIUcIBYlLDGvseKjCuhfc=; h=From:To:Cc:Subject:Date:Reply-To; b=UrlaC/rJSK5ZBUfMNgvtGWWYCwE2c3Zmhodqky6hlRezeL1PTCnK5Dyw7/nGrZATL mDe8blt1s1Yt1PsnV3qP4q666tlZKGUC4kBOTI55r3oD4lZQ2gatlkKr0VbboI2MeN SJ5XcScEvszLrBXgMCcXu7GDgAmJY9PhPNmqt9tg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99080: fs: Free any excess xarray nodes in clear_inode() Date: Fri, 23 Oct 2026 14:21:22 +0200 Message-ID: <2026102336-CVE-2026-99080-12f4@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=2337; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=1Z4VATkGJztRgEDZ6ngiv4LTSBEay4w0dQUSl/e5h4Y=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm3A27M8lyb/4tpyf+7GZnX/I5aFz3zmfPQfsJNllVn/ 7ldjr28oyOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAm0mrEsGDKwfdx/f/kNoln 2DmvYT0VpGT4KYBhwa61FuX7ZjL/z7B9JtYr3sUloGbcBAA= 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: fs: Free any excess xarray nodes in clear_inode() For many years we've had a hard to hit leak of xarray nodes. Hugh documented it well in commit 786b31121a2c. Recently people and syzbot have found ways to force it to happen with madvise. Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock. The Linux kernel CVE team has assigned CVE-2026-99080 to this issue. Affected and fixed versions =========================== Fixed in 6.6.160 with commit f1c966eb6ed5e190c90a56c5bdaa69967de39f21 Fixed in 6.12.113 with commit 21f51434c47d8628b62275ae6c6ad6b573abcd02 Fixed in 6.18.57 with commit 50cff3f112d64db6e5f57355f79bc837db8fe132 Fixed in 7.2.11 with commit 43f830e2bb84b22ca824b20bb861d823ecb520bd Fixed in 7.3 with commit ee3f011250104129893d8e9599147e457d4d7280 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-99080 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/inode.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/f1c966eb6ed5e190c90a56c5bdaa69967de39f21 https://git.kernel.org/stable/c/21f51434c47d8628b62275ae6c6ad6b573abcd02 https://git.kernel.org/stable/c/50cff3f112d64db6e5f57355f79bc837db8fe132 https://git.kernel.org/stable/c/43f830e2bb84b22ca824b20bb861d823ecb520bd https://git.kernel.org/stable/c/ee3f011250104129893d8e9599147e457d4d7280