From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Edward Adam Davis <eadavis@qq.com>,
syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com
Cc: jlbec@evilplan.org, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] ocfs2: Add i_size check for dir
Date: Tue, 20 Aug 2024 20:44:37 +0800 [thread overview]
Message-ID: <205e0d29-2567-4d82-a024-a8e7826d9f18@linux.alibaba.com> (raw)
In-Reply-To: <tencent_EC9ACDC0793A6F742D7D6FA094F0E96AEF0A@qq.com>
On 8/20/24 8:08 PM, Edward Adam Davis wrote:
> When the i_size of dir is too large, it will cause limit to overflow and
> be less than de_buf, ultimately resulting in last_de not being initialized
> and causing uaf issue.
>
> Reported-and-tested-by: syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
> fs/ocfs2/dir.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/ocfs2/dir.c b/fs/ocfs2/dir.c
> index d620d4c53c6f..c308dba6d213 100644
> --- a/fs/ocfs2/dir.c
> +++ b/fs/ocfs2/dir.c
> @@ -3343,6 +3343,8 @@ static int ocfs2_find_dir_space_id(struct inode *dir, struct buffer_head *di_bh,
> unsigned long offset = 0;
> unsigned int rec_len, new_rec_len, free_space;
>
> + if (i_size_read(dir) > OCFS2_MAX_BLOCKSIZE)
> + return -EINVAL;
Why OCFS2_MAX_BLOCKSIZE?
It seems that this is caused by a corrupted dir inode, since this is an
inline case, we may try best to make sure it won't exceeds block size?
i.e. dir->i_sb->s_blocksize.
Thanks,
Joseph
> /*
> * This calculates how many free bytes we'd have in block zero, should
> * this function force expansion to an extent tree.
next prev parent reply other threads:[~2024-08-20 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 7:58 [syzbot] [ocfs2?] general protection fault in ocfs2_prepare_dir_for_insert syzbot
2024-08-20 11:19 ` Edward Adam Davis
2024-08-20 11:42 ` syzbot
2024-08-20 12:08 ` [PATCH] ocfs2: Add i_size check for dir Edward Adam Davis
2024-08-20 12:44 ` Joseph Qi [this message]
2024-08-20 13:55 ` Edward Adam Davis
2024-08-21 10:41 ` Joseph Qi
2024-08-21 11:15 ` Edward Adam Davis
2024-08-20 14:59 ` Matthew Wilcox
2024-08-21 6:16 ` heming.zhao
2024-08-21 9:08 ` Edward Adam Davis
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=205e0d29-2567-4d82-a024-a8e7826d9f18@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=eadavis@qq.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+5a64828fcc4c2ad9b04f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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®