All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98445: xfs: don't let memory failures leak blocks and kill repairs
Date: Sun, 18 Oct 2026 17:15:09 +0200	[thread overview]
Message-ID: <2026101807-CVE-2026-98445-afa2@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

xfs: don't let memory failures leak blocks and kill repairs

LOLLM complains that a memory allocation failure in
xrep_newbt_add_blocks results in online repair leaking blocks that were
previously allocated to write a new btree, but the problem is worse than
that -- a limitation of the codebase is that the callers cannot undo the
transaction /and/ return the error -- either you undo all changes and
commit the transaction, or you error out and the filesystem goes down.

However, the new btree space reservation object isn't that big (~48
bytes).  Let's just do a NOFAIL allocation and the problem goes away.

The Linux kernel CVE team has assigned CVE-2026-98445 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 6.12.113 with commit 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50
	Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 6.18.56 with commit b15c79fca28060fd9c7e77f2c3ebc4ba023974e8
	Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 7.2.9 with commit 0e0d3372a84029da1768c7a4c4601484af5b58a2
	Issue introduced in 6.8 with commit be408417630427984a1fddd069f30b245793234c and fixed in 7.3-rc5 with commit ab1c416d2377cdc16123ef521aac4da1c468c3d4

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-98445
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/newbt.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/3380151cf0ce8ad0c1d356fed51e4b69e1d28e50
	https://git.kernel.org/stable/c/b15c79fca28060fd9c7e77f2c3ebc4ba023974e8
	https://git.kernel.org/stable/c/0e0d3372a84029da1768c7a4c4601484af5b58a2
	https://git.kernel.org/stable/c/ab1c416d2377cdc16123ef521aac4da1c468c3d4

                 reply	other threads:[~2026-10-18 15:21 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=2026101807-CVE-2026-98445-afa2@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.