From: "Darrick J. Wong" <djwong@kernel.org>
To: Hongling Zeng <zenghongling@kylinos.cn>
Cc: cem@kernel.org, chandanrlinux@gmail.com,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
zhongling0719@126.com, stable@vger.kernel.org
Subject: Re: [PATCH v3] xfs: fix heap buffer overflow in xfs_bmbt_to_bmdr
Date: Thu, 30 Jul 2026 08:43:09 -0700 [thread overview]
Message-ID: <20260730154309.GB3556460@frogsfrogsfrogs> (raw)
In-Reply-To: <20260730094824.200669-1-zenghongling@kylinos.cn>
Please take a breath and refrain from sending the same patch three times
in ninety minutes. Figure out what you want to change, run it through
some testing, and only send it once you've stopped finding things to
tweak.
--D
On Thu, Jul 30, 2026 at 05:48:24PM +0800, Hongling Zeng wrote:
> The xfs_bmbt_to_bmdr() function converts an in-memory btree root to
> on-disk form during log recovery. It uses bb_numrecs from the source
> to determine memcpy size without validating against the destination
> fork capacity.
>
> Current code:
> dmxr = xfs_bmdr_maxrecs(dblocklen, 0); // destination capacity
> ...
> dmxr = be16_to_cpu(dblock->bb_numrecs); // overwrite with source value!
> memcpy(..., * dmxr); // may overflow destination!
>
> If bb_numrecs is larger than the destination fork capacity,
> memcpy writes beyond the fork buffer, causing heap overflow.
>
> Fix by validating bb_numrecs against the destination capacity
> before using it for memcpy operations.
>
> Cc: stable@vger.kernel.org
> Fixes: 8ea5682d0711 ("xfs: refactor log recovery item dispatch for pass2 readhead functions")
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
> ---
> Change in v3:
> - Use dmxr for tpp calculation (on-disk format) and nrecs for memcpy (actual records)
> ---
> Change in v2:
> - Ensure memcpy operations consistently use nrecs instead of dmxr.
> ---
> fs/xfs/libxfs/xfs_bmap_btree.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap_btree.c b/fs/xfs/libxfs/xfs_bmap_btree.c
> index 758a4b1ccf5b..a119053d67b5 100644
> --- a/fs/xfs/libxfs/xfs_bmap_btree.c
> +++ b/fs/xfs/libxfs/xfs_bmap_btree.c
> @@ -151,6 +151,7 @@ xfs_bmbt_to_bmdr(
> int dmxr;
> xfs_bmbt_key_t *fkp;
> __be64 *fpp;
> + int nrecs;
> xfs_bmbt_key_t *tkp;
> __be64 *tpp;
>
> @@ -167,14 +168,19 @@ xfs_bmbt_to_bmdr(
> ASSERT(rblock->bb_level != 0);
> dblock->bb_level = rblock->bb_level;
> dblock->bb_numrecs = rblock->bb_numrecs;
> +
> + /* Validate record count against destination fork capacity */
> + nrecs = be16_to_cpu(rblock->bb_numrecs);
> dmxr = xfs_bmdr_maxrecs(dblocklen, 0);
> + if (nrecs > dmxr)
> + return;
> +
> fkp = xfs_bmbt_key_addr(mp, rblock, 1);
> tkp = xfs_bmdr_key_addr(dblock, 1);
> fpp = xfs_bmap_broot_ptr_addr(mp, rblock, 1, rblocklen);
> tpp = xfs_bmdr_ptr_addr(dblock, 1, dmxr);
> - dmxr = be16_to_cpu(dblock->bb_numrecs);
> - memcpy(tkp, fkp, sizeof(*fkp) * dmxr);
> - memcpy(tpp, fpp, sizeof(*fpp) * dmxr);
> + memcpy(tkp, fkp, sizeof(*fkp) * nrecs);
> + memcpy(tpp, fpp, sizeof(*fpp) * nrecs);
> }
>
> STATIC struct xfs_btree_cur *
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2026-07-30 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 9:48 Hongling Zeng
2026-07-30 15:43 ` Darrick J. Wong [this message]
2026-07-31 1:22 ` Hongling Zeng
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=20260730154309.GB3556460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=chandanrlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zenghongling@kylinos.cn \
--cc=zhongling0719@126.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®