From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Heming Zhao <heming.zhao@suse.com>,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: fix out-of-bounds write in ocfs2_write_end_inline
Date: Thu, 2 Apr 2026 23:48:15 -0700 [thread overview]
Message-ID: <20260402234815.1c0070c4e379c6c244314949@linux-foundation.org> (raw)
In-Reply-To: <20260403063830.3662739-1-joseph.qi@linux.alibaba.com>
On Fri, 3 Apr 2026 14:38:30 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
> KASAN reports a use-after-free write of 4086 bytes in
> ocfs2_write_end_inline, called from ocfs2_write_end_nolock during a
> copy_file_range splice fallback on a corrupted ocfs2 filesystem mounted
> on a loop device. The actual bug is an out-of-bounds write past the
> inode block buffer, not a true use-after-free. The write overflows into
> an adjacent freed page, which KASAN reports as UAF.
>
> The root cause is that ocfs2_try_to_write_inline_data trusts the
> on-disk id_count field to determine whether a write fits in inline
> data. On a corrupted filesystem, id_count can exceed the physical
> maximum inline data capacity, causing writes to overflow the inode
> block buffer.
>
> Call trace (crash path):
>
> vfs_copy_file_range (fs/read_write.c:1634)
> do_splice_direct
> splice_direct_to_actor
> iter_file_splice_write
> ocfs2_file_write_iter
> generic_perform_write
> ocfs2_write_end
> ocfs2_write_end_nolock (fs/ocfs2/aops.c:1949)
> ocfs2_write_end_inline (fs/ocfs2/aops.c:1915)
> memcpy_from_folio <-- KASAN: write OOB
>
> So add id_count upper bound check in ocfs2_validate_inode_block() to
> alongside the existing i_size check to fix it.
Thanks.
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -1505,6 +1505,16 @@ int ocfs2_validate_inode_block(struct super_block *sb,
> goto bail;
> }
>
> + if (le16_to_cpu(data->id_count) >
> + ocfs2_max_inline_data_with_xattr(sb, di)) {
> + rc = ocfs2_error(sb,
> + "Invalid dinode #%llu: inline data id_count %u exceeds max %d\n",
> + (unsigned long long)bh->b_blocknr,
> + le16_to_cpu(data->id_count),
> + ocfs2_max_inline_data_with_xattr(sb, di));
> + goto bail;
> + }
> +
> if (le64_to_cpu(di->i_size) > le16_to_cpu(data->id_count)) {
> rc = ocfs2_error(sb,
> "Invalid dinode #%llu: inline data i_size %llu exceeds id_count %u\n",
Even though the surrounding code is from 2025 (1524af3685b35), I think
this bug predates 1524af3685b35?
If so, I expect the -stable people will have trouble backporting this.
If so, they'll report it and shall ask for a reworked version.
next prev parent reply other threads:[~2026-04-03 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 6:38 Joseph Qi
2026-04-03 6:48 ` Andrew Morton [this message]
2026-04-03 7:03 ` Joseph Qi
2026-04-03 19:28 ` Andrew Morton
2026-04-07 1:27 ` Joseph Qi
2026-04-07 14:26 ` Heming Zhao
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=20260402234815.1c0070c4e379c6c244314949@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=heming.zhao@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
/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®