From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99398: xfs: always forget cached ACLs if the attr fork swap succeeds
Date: Thu, 19 Nov 2026 15:24:56 +0100 [thread overview]
Message-ID: <2026111956-CVE-2026-99398-2425@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-11-19 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026111956-CVE-2026-99398-2425@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.