From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80538: xfs: propagate errors from xfs_rtginode_load
Date: Wed, 26 Aug 2026 16:37:34 +0200 [thread overview]
Message-ID: <2026082605-CVE-2026-80538-30fb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xfs: propagate errors from xfs_rtginode_load
xfs_rtginode_ensure() treats every xfs_rtginode_load() error other than
-ENOENT as success. This can leave the realtime group inode unset after an
I/O, allocation, or corruption error. Growfs then continues as though the
inode had been loaded.
Only -ENOENT means that the inode needs to be created. Return all other
errors to the growfs caller.
The Linux kernel CVE team has assigned CVE-2026-80538 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit ae897e0bed0f5461a6b1c3259c7d899759ba2a62 and fixed in 6.18.46 with commit ec19cea4ef1ce9d6e2e3f7e9e7bf88ede31176e7
Issue introduced in 6.13 with commit ae897e0bed0f5461a6b1c3259c7d899759ba2a62 and fixed in 7.1.10 with commit 61c5165f02deb2eed9b6b539bb279e6629fee652
Issue introduced in 6.13 with commit ae897e0bed0f5461a6b1c3259c7d899759ba2a62 and fixed in 7.2 with commit b7e53968cb8882c2d276429ea8550848a4940874
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-80538
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/xfs_rtalloc.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/ec19cea4ef1ce9d6e2e3f7e9e7bf88ede31176e7
https://git.kernel.org/stable/c/61c5165f02deb2eed9b6b539bb279e6629fee652
https://git.kernel.org/stable/c/b7e53968cb8882c2d276429ea8550848a4940874
reply other threads:[~2026-08-26 14:40 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=2026082605-CVE-2026-80538-30fb@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.