From: "Darrick J. Wong" <djwong@kernel.org>
To: Ibrahim Hashimov <security@auditcode.ai>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org, bfoster@redhat.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] xfs: bounds-check buffer log item's dirty bitmap
Date: Tue, 14 Jul 2026 10:43:07 -0700 [thread overview]
Message-ID: <20260714174307.GE7380@frogsfrogsfrogs> (raw)
In-Reply-To: <20260714172730.73160-1-security@auditcode.ai>
On Tue, Jul 14, 2026 at 07:27:30PM +0200, Ibrahim Hashimov wrote:
> xlog_recover_do_reg_buffer() replays each dirty region described by a
> buffer log item's bitmap into the buffer read for that item:
>
> memcpy(xfs_buf_offset(bp, (uint)bit << XFS_BLF_SHIFT),
> item->ri_buf[i].iov_base,
> nbits << XFS_BLF_SHIFT);
>
> The destination offset (bit/nbits, from the logged dirty bitmap) and the
> buffer size (from the logged blf_len) are both attacker-controlled and
> otherwise unrelated, yet the only thing bounding the copy is an ASSERT(),
> which compiles away on production kernels. A crafted image logging a
> small blf_len together with a bitmap bit past the end of that buffer
> drives the memcpy() past the buffer's allocation, corrupting adjacent
> kernel heap during mount-time log recovery. This is reachable by anyone
> who can get a crafted image mounted -- the malicious-filesystem threat
> model XFS already guards against elsewhere.
>
> Turn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery
> of the buffer with -EFSCORRUPTED, consistent with the validate-and-fail
> idiom already used in xlog_recover_do_inode_buffer() and
> xfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes
> STATIC int and its three callers propagate the error.
>
> Found and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted
> image trips a slab-out-of-bounds write before this change and fails
> recovery cleanly with -EFSCORRUPTED after it.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ibrahim Hashimov <security@auditcode.ai>
> Assisted-by: AuditCode-AI:2026.07
> ---
> v3: trim the changelog per Brian Foster's review; no code change. Add a
> Fixes: tag -- the destination-bounds check has been an ASSERT since
> the initial git import (2.6.12-rc2), so it predates the git era.
> v2: resend; v1 went out with an empty Subject line due to a local
> git send-email glitch (leading blank line in the patch file).
>
> fs/xfs/xfs_buf_item_recover.c | 48 ++++++++++++++++++++++++++++-------
> 1 file changed, 39 insertions(+), 9 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf_item_recover.c b/fs/xfs/xfs_buf_item_recover.c
> index 02b95b89d1b5..521e5f544caf 100644
> --- a/fs/xfs/xfs_buf_item_recover.c
> +++ b/fs/xfs/xfs_buf_item_recover.c
> @@ -461,7 +461,7 @@ xlog_recover_validate_buf_type(
> * given buffer. The bitmap in the buf log format structure indicates
> * where to place the logged data.
> */
> -STATIC void
> +STATIC int
> xlog_recover_do_reg_buffer(
> struct xfs_mount *mp,
> struct xlog_recover_item *item,
> @@ -489,8 +489,25 @@ xlog_recover_do_reg_buffer(
> ASSERT(nbits > 0);
> ASSERT(item->ri_buf[i].iov_base != NULL);
> ASSERT(item->ri_buf[i].iov_len % XFS_BLF_CHUNK == 0);
> - ASSERT(BBTOB(bp->b_length) >=
> - ((uint)bit << XFS_BLF_SHIFT) + (nbits << XFS_BLF_SHIFT));
> +
> + /*
> + * The bitmap is only trustworthy to the extent that it
> + * describes a region that actually fits inside the buffer we
> + * read in based on the (attacker-controlled) blf_len. Do not
> + * rely on an ASSERT() for this -- it compiles away entirely
> + * on non-DEBUG kernels, which is exactly where this matters,
> + * so validate it for real and abort recovery of this buffer
> + * rather than copying past the end of it.
> + */
> + if (XFS_IS_CORRUPT(mp, BBTOB(bp->b_length) <
> + ((uint)bit << XFS_BLF_SHIFT) +
> + (nbits << XFS_BLF_SHIFT))) {
> + xfs_alert(mp,
> + "Bad buffer log item dirty bitmap (bit %d, nbits %d) for %d-byte buffer at daddr 0x%llx.",
> + bit, nbits, BBTOB(bp->b_length),
> + xfs_buf_daddr(bp));
> + return -EFSCORRUPTED;
> + }
>
> /*
> * The dirty regions logged in the buffer, even though
> @@ -544,6 +561,7 @@ xlog_recover_do_reg_buffer(
> ASSERT(i == item->ri_total);
>
> xlog_recover_validate_buf_type(mp, bp, buf_f, current_lsn);
> + return 0;
> }
>
> /*
> @@ -553,7 +571,9 @@ xlog_recover_do_reg_buffer(
> * Else, treat it as a regular buffer and do recovery.
> *
> * Return false if the buffer was tossed and true if we recovered the buffer to
> - * indicate to the caller if the buffer needs writing.
> + * indicate to the caller if the buffer needs writing. *error is set if
> + * recovery of the buffer failed and the caller must abort replay of this
> + * buffer.
This is still a rather ugly function signature. You could compress the
return value into "1 if dirty, 0 if clean, or a negative errno on
failure" and then the callsite becomes:
error = xlog_recover_do_dquot_buffer(...):
if (error <= 0)
goto out_release;
/* write dirty buffer */
error = 0;
--D
> */
> STATIC bool
> xlog_recover_do_dquot_buffer(
> @@ -561,10 +581,12 @@ xlog_recover_do_dquot_buffer(
> struct xlog *log,
> struct xlog_recover_item *item,
> struct xfs_buf *bp,
> - struct xfs_buf_log_format *buf_f)
> + struct xfs_buf_log_format *buf_f,
> + int *error)
> {
> uint type;
>
> + *error = 0;
> trace_xfs_log_recover_buf_dquot_buf(log, buf_f);
>
> /*
> @@ -586,7 +608,7 @@ xlog_recover_do_dquot_buffer(
> if (log->l_quotaoffs_flag & type)
> return false;
>
> - xlog_recover_do_reg_buffer(mp, item, bp, buf_f, NULLCOMMITLSN);
> + *error = xlog_recover_do_reg_buffer(mp, item, bp, buf_f, NULLCOMMITLSN);
> return true;
> }
>
> @@ -724,7 +746,9 @@ xlog_recover_do_primary_sb_buffer(
> xfs_rgnumber_t orig_rgcount = mp->m_sb.sb_rgcount;
> int error;
>
> - xlog_recover_do_reg_buffer(mp, item, bp, buf_f, current_lsn);
> + error = xlog_recover_do_reg_buffer(mp, item, bp, buf_f, current_lsn);
> + if (error)
> + return error;
>
> if (orig_agcount == 0) {
> xfs_alert(mp, "Trying to grow file system without AGs");
> @@ -1083,7 +1107,10 @@ xlog_recover_buf_commit_pass2(
> (XFS_BLF_UDQUOT_BUF|XFS_BLF_PDQUOT_BUF|XFS_BLF_GDQUOT_BUF)) {
> bool dirty;
>
> - dirty = xlog_recover_do_dquot_buffer(mp, log, item, bp, buf_f);
> + dirty = xlog_recover_do_dquot_buffer(mp, log, item, bp, buf_f,
> + &error);
> + if (error)
> + goto out_release;
> if (!dirty)
> goto out_release;
> } else if ((xfs_blft_from_flags(buf_f) & XFS_BLFT_SB_BUF) &&
> @@ -1105,7 +1132,10 @@ xlog_recover_buf_commit_pass2(
> xfs_buf_relse(rtsb_bp);
> }
> } else {
> - xlog_recover_do_reg_buffer(mp, item, bp, buf_f, current_lsn);
> + error = xlog_recover_do_reg_buffer(mp, item, bp, buf_f,
> + current_lsn);
> + if (error)
> + goto out_release;
> }
>
> /*
> --
> 2.50.1 (Apple Git-155)
>
>
next prev parent reply other threads:[~2026-07-14 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 22:58 [PATCH v2] xfs: bounds-check buffer log item's dirty bitmap Ibrahim Hashimov
2026-07-14 15:08 ` Brian Foster
2026-07-14 17:27 ` [PATCH v3] " Ibrahim Hashimov
2026-07-14 17:43 ` Darrick J. Wong [this message]
2026-07-14 17:55 ` [PATCH v4] " Ibrahim Hashimov
2026-07-14 18:01 ` Darrick J. Wong
2026-07-14 19:20 ` Brian Foster
2026-07-14 19:40 ` Darrick J. Wong
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=20260714174307.GE7380@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=security@auditcode.ai \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox