From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80820: xfs: don't livelock in scrub on a circular unlinked list
Date: Fri, 4 Sep 2026 17:11:59 +0200 [thread overview]
Message-ID: <2026090413-CVE-2026-80820-d37e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xfs: don't livelock in scrub on a circular unlinked list
LOLLM points out that online fsck can livelock if an unlinked inode list
contains a loop. Use a bitmap to detect cycles.
The Linux kernel CVE team has assigned CVE-2026-80820 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.15 with commit a12890aebb895951720ff884eab1c99a30645b29 and fixed in 6.12.106 with commit 599453f83458b57995290a1d31200c263e2c2691
Issue introduced in 4.15 with commit a12890aebb895951720ff884eab1c99a30645b29 and fixed in 6.18.47 with commit 159d162fe80bd56573cafde5801bd5a90a3dd1ac
Issue introduced in 4.15 with commit a12890aebb895951720ff884eab1c99a30645b29 and fixed in 7.1.11 with commit 56407a61a8bb85b884de802d39635abdb0ea7408
Issue introduced in 4.15 with commit a12890aebb895951720ff884eab1c99a30645b29 and fixed in 7.2 with commit 527eaaefddb6ec5c83a06c9a1559960dd6361753
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-80820
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/agheader.c
fs/xfs/scrub/agheader_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/599453f83458b57995290a1d31200c263e2c2691
https://git.kernel.org/stable/c/159d162fe80bd56573cafde5801bd5a90a3dd1ac
https://git.kernel.org/stable/c/56407a61a8bb85b884de802d39635abdb0ea7408
https://git.kernel.org/stable/c/527eaaefddb6ec5c83a06c9a1559960dd6361753
reply other threads:[~2026-09-04 15:19 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=2026090413-CVE-2026-80820-d37e@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.