From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99689: xfs: fix temporary cursor leak in btree shift corruption paths
Date: Fri, 20 Nov 2026 06:51:15 +0100 [thread overview]
Message-ID: <2026112057-CVE-2026-99689-bf59@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix temporary cursor leak in btree shift corruption paths
In xfs_btree_lshift and xfs_btree_rshift, when XFS_IS_CORRUPT detects
an invalid firstrec/lastrec result after xfs_btree_dup_cursor has
successfully allocated a temporary cursor, the error path jumps to
error0 which returns without freeing tcur. This leaks the cursor
memory, the xfs_group reference, and the per-level buffer references
held by the duplicated cursor. Jump to error1 instead, which calls
xfs_btree_del_cursor(tcur, XFS_BTREE_ERROR) to properly release all
resources.
The Linux kernel CVE team has assigned CVE-2026-99689 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 6.12.118 with commit 3f52eb7dd4a584c60f1b190b18fa4958b5fbef65
Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 6.18.64 with commit fa4189dbbd9487de3ef9437572a29c71c5521fe5
Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 7.3.5 with commit 845ef1a6277f8b8bdf6479c6f561c16e5d5f56e2
Issue introduced in 2.6.29 with commit 9eaead51bed957af0070a277d945744a76df0c8b and fixed in 7.4-rc2 with commit 2bbca049deeb1699cafd966cb2793fee576ee409
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-99689
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/libxfs/xfs_btree.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/3f52eb7dd4a584c60f1b190b18fa4958b5fbef65
https://git.kernel.org/stable/c/fa4189dbbd9487de3ef9437572a29c71c5521fe5
https://git.kernel.org/stable/c/845ef1a6277f8b8bdf6479c6f561c16e5d5f56e2
https://git.kernel.org/stable/c/2bbca049deeb1699cafd966cb2793fee576ee409
reply other threads:[~2026-11-20 5:57 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=2026112057-CVE-2026-99689-bf59@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.