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=1795099492; b=zlGmjeR7eI7scTp5QwpozjDrR+ykgz/EwPM4LyKDnBSEkPys09/zQDUcl3PAjXSLBDtZ aAXzPqKgQFpoVvy0XHUxOjE3wKtfVM5Xd58+o/9+Vv7vgvA6mQaPWCLcxMwto/Lz3aDAm Lrq5bujCsvGZ9D/4N8aE/XkeQZBW92qXvWHZgkWhn8W9ZMY3qyxoxJ6TUYpmltiYr107g 6dPvERGCz4RnrB9Mvmf0Z2wRwtYWUKonkYJt3dRhLBmAdcJHp0qPHCUAqapTwaxeFweuV F0SRt/3cQgVup2599GJHqaRnL3nxyhSLOUcOrRsW/X1mL6V8+YYvb35YdGT4jTbkjkA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099492; 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=if2L1Cb4YIX9DjomodI+nauHM5tmLAVpPg5av3AuqfI=; b=EY4HVdFsEiTGzGNDjvQDCWHZtvJk/q3w1F+Ieubez7l6U5wdwO9gkuwgmKHQ/a1EFkL+ aMLtxq4ULRNiYPxQddJWXY2LLbaBqC2FDLr4gLW78r7o8CpawLU7O5OUtRLf+w0HH3Pyw 3+R6P27rY/lYpvxplXFPBKWSLlOXPO/U3t9rq0h/USk3pFAqcgYhSD9TUhlVJzB7sSddm E3464J4Toz8PgmGhOFkiTmrbUtHW3UhzZCztcjVEnZ73bQG9EC3RPYEHhGvRIlTdHlDta WUYQGbersqui2nYHJoe2UfLdhOIAiclcmdMGarTDAsGPTO1tSWjBTdZrQ072WnVv0DA== 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=wYhWuu7k; 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 2E747606A320 for ; Thu, 19 Nov 2026 14:44:52 +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=wYhWuu7k Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4D8DD1F000CD; Thu, 19 Nov 2026 14:44:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099492; bh=if2L1Cb4YIX9DjomodI+nauHM5tmLAVpPg5av3AuqfI=; h=From:To:Cc:Subject:Date:Reply-To; b=wYhWuu7kPo25mwtjl1z9f7gD28618uiuRP99QX/Y955vGfjLbEwRkW/oLiidrp6zt niMad+Lh/Jk0IAsDHir8XrxdIvZYrveJOHbqqouaIyD2D8vJHvc2kSNq7eID6Dr61N haE5A7CGlJpjkuLc9NQftInkTsD5FdYQi26Ay0/c= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99398: xfs: always forget cached ACLs if the attr fork swap succeeds Date: Thu, 19 Nov 2026 15:24:56 +0100 Message-ID: <2026111956-CVE-2026-99398-2425@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=2586; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=cw5GHQCEtDfvb+Mvn3cnDtzno2KCOoGZL0AWXeB7z6s=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2WrnV6uyVc84HjAreAYDR76T3QGrt9NF8g8/2HphV e+UliPPO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi3PcZ5vAZL7k8K0FLTk8s yKpA4jQb9yuOOQzzw58F5X3vf3bhyd8DPR1TVn9fMn/qbQA= 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: always forget cached ACLs if the attr fork swap succeeds LOLLM complains that xrep_xattr_rebuild_tree omits the xfs_forget_acl call if the attr fork swap succeeds (and hence the acls might have changed) but reaping the old attr fork fails. Fix it so that we always purge the cached acls if the swap succeeds, even if subsequent steps do not. This avoids some cache coherency problems with access controls. The Linux kernel CVE team has assigned CVE-2026-99398 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit e47dcf113ae348678143cc935a1183059c02c9ad and fixed in 6.12.117 with commit f56d0d49f555db88cac92b20dcc988664c72c280 Issue introduced in 6.10 with commit e47dcf113ae348678143cc935a1183059c02c9ad and fixed in 6.18.61 with commit 8cce27911eb3f8bb16f04b0a913277de6b7506b4 Issue introduced in 6.10 with commit e47dcf113ae348678143cc935a1183059c02c9ad and fixed in 7.3.2 with commit 2430132937e9ce5c6144db0de27439c31d189229 Issue introduced in 6.10 with commit e47dcf113ae348678143cc935a1183059c02c9ad and fixed in 7.4-rc1 with commit 41ee987f53785b9443388a756912b1a0fe3c9592 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-99398 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/attr_repair.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/f56d0d49f555db88cac92b20dcc988664c72c280 https://git.kernel.org/stable/c/8cce27911eb3f8bb16f04b0a913277de6b7506b4 https://git.kernel.org/stable/c/2430132937e9ce5c6144db0de27439c31d189229 https://git.kernel.org/stable/c/41ee987f53785b9443388a756912b1a0fe3c9592