From: Zhang Yi <yi.zhang@huawei.com>
To: Pei Li <peili.dev@gmail.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<skhan@linuxfoundation.org>, <syzkaller-bugs@googlegroups.com>,
<linux-kernel-mentees@lists.linuxfoundation.org>,
<syzbot+2cab87506a0e7885f4b9@syzkaller.appspotmail.com>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: [PATCH v2] Fix WARNING in __ext4_ioctl
Date: Wed, 3 Jul 2024 09:24:41 +0800 [thread overview]
Message-ID: <154c52ab-2452-df90-a8d8-5b786f46041b@huawei.com> (raw)
In-Reply-To: <20240702-bug8-v2-1-be675f490db1@gmail.com>
On 2024/7/3 8:07, Pei Li wrote:
> Specify the size of s_volume_name in strscpy_pad() to avoid buffer
> overflow.
>
> strscpy_pad() by default takes the size of destination string as the
> size to be read from source string. However, as s_volume_name is only
> declared as an array of size EXT4_LABEL_MAX, we are reading 1 byte more
> than expected.
>
> Reported-by: syzbot+2cab87506a0e7885f4b9@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=2cab87506a0e7885f4b9
> Fixes: 744a56389f73 ("ext4: replace deprecated strncpy with alternatives")
> Signed-off-by: Pei Li <peili.dev@gmail.com>
Thanks for the fix, it looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> strscpy_pad() by default takes the size of destination string as the
> size to be read from source string. However, as s_volume_name is only
> declared as an array of size EXT4_LABEL_MAX, we are reading 1 byte more
> than expected.
>
> Specify the size of s_volume_name in strscpy_pad() to avoid buffer
> overflow.
> ---
> Changes in v2:
> - Add fixes label
> - Move workaround into commit log
> - Link to v1: https://lore.kernel.org/r/20240628-bug8-v1-1-417ef53cca33@gmail.com
> ---
> fs/ext4/ioctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c
> index dab7acd49709..0c4fb579757a 100644
> --- a/fs/ext4/ioctl.c
> +++ b/fs/ext4/ioctl.c
> @@ -1151,7 +1151,7 @@ static int ext4_ioctl_getlabel(struct ext4_sb_info *sbi, char __user *user_label
> BUILD_BUG_ON(EXT4_LABEL_MAX >= FSLABEL_MAX);
>
> lock_buffer(sbi->s_sbh);
> - strscpy_pad(label, sbi->s_es->s_volume_name);
> + strscpy_pad(label, sbi->s_es->s_volume_name, EXT4_LABEL_MAX);
> unlock_buffer(sbi->s_sbh);
>
> if (copy_to_user(user_label, label, sizeof(label)))
>
> ---
> base-commit: 55027e689933ba2e64f3d245fb1ff185b3e7fc81
> change-id: 20240628-bug8-7f700a228c4a
>
> Best regards,
>
next prev parent reply other threads:[~2024-07-03 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 0:07 [PATCH v2] Fix WARNING in __ext4_ioctl Pei Li
2024-07-03 1:24 ` Zhang Yi [this message]
2024-07-11 2:42 ` Theodore Ts'o
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=154c52ab-2452-df90-a8d8-5b786f46041b@huawei.com \
--to=yi.zhang@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peili.dev@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+2cab87506a0e7885f4b9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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