From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org, heming.zhao@suse.com
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
syzbot+c897823f699449cc3eb4@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] ocfs2: validate inline data i_size during inode read
Date: Fri, 12 Dec 2025 12:49:04 +0800 [thread overview]
Message-ID: <b3f7d236-0879-445f-8f46-09045f37ec99@linux.alibaba.com> (raw)
In-Reply-To: <20251212040400.6377-1-kartikey406@gmail.com>
On 2025/12/12 12:04, Deepanshu Kartikey wrote:
> When reading an inode from disk, ocfs2_validate_inode_block() performs
> various sanity checks but does not validate the size of inline data.
> If the filesystem is corrupted, an inode's i_size can exceed the actual
> inline data capacity (id_count).
>
> This causes ocfs2_dir_foreach_blk_id() to iterate beyond the inline
> data buffer, triggering a use-after-free when accessing directory
> entries from freed memory.
>
> In the syzbot report:
> - i_size was 1099511627576 bytes (~1TB)
> - Actual inline data capacity (id_count) is typically <256 bytes
> - A garbage rec_len (54648) caused ctx->pos to jump out of bounds
> - This triggered a UAF in ocfs2_check_dir_entry()
>
> Fix by adding a validation check in ocfs2_validate_inode_block() to
> ensure inodes with inline data have i_size <= id_count. This catches
> the corruption early during inode read and prevents all downstream
> code from operating on invalid data.
>
> Reported-by: syzbot+c897823f699449cc3eb4@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c897823f699449cc3eb4
> Tested-by: syzbot+c897823f699449cc3eb4@syzkaller.appspotmail.com
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> ---
> v2:
> - Removed unnecessary S_ISDIR() check since OCFS2_INLINE_DATA_FL
> applies to both directories and regular files (Heming Zhao)
> - Fixed checkpatch.pl warnings
> - Updated commit message to say "inline data" instead of
> "inline directory"
> ---
> fs/ocfs2/inode.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index 8340525e5589..1fac457cb04a 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -1521,6 +1521,23 @@ int ocfs2_validate_inode_block(struct super_block *sb,
> }
> }
>
> + /*
> + * Validate inline data size. If the inode has inline data,
> + * i_size must not exceed the inline data capacity.
> + */
> + if (di->i_dyn_features & cpu_to_le16(OCFS2_INLINE_DATA_FL)) {
Since we've already have a branch to checking OCFS2_INLINE_DATA_FL, why not
fold them together?
Thanks,
Joseph
> + struct ocfs2_inline_data *data = &di->id2.i_data;
> +
> + 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",
> + (unsigned long long)bh->b_blocknr,
> + (unsigned long long)le64_to_cpu(di->i_size),
> + le16_to_cpu(data->id_count));
> + goto bail;
> + }
> + }
> +
> rc = 0;
>
> bail:
prev parent reply other threads:[~2025-12-12 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 4:04 [PATCH v2] ocfs2: validate inline data i_size during inode read Deepanshu Kartikey
2025-12-12 4:49 ` Joseph Qi [this message]
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=b3f7d236-0879-445f-8f46-09045f37ec99@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+c897823f699449cc3eb4@syzkaller.appspotmail.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