All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Edward Adam Davis <eadavis@qq.com>,
	syzbot+0192952caa411a3be209@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	mchehab@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] media: az6007: Add upper bound check to the data of device state
Date: Mon, 3 Nov 2025 11:06:21 +0100	[thread overview]
Message-ID: <d661ae00-d100-46ef-8a15-50919b34daae@kernel.org> (raw)
In-Reply-To: <tencent_93C4465D499DEEDF6EE60CB667DC46D0D206@qq.com>

On 21/04/2025 16:31, Edward Adam Davis wrote:
> syzbot report a corrupted list in az6007_i2c_xfer. [1]
> 
> Before accessing the member data of the struct az6007_device_state, only
> the lower boundary of data is checked, but the upper boundary is not checked.
> When the value of msgs[i].len is damaged or too large, it will cause out
> of bounds access to st->data.
> 
> [1]
> UBSAN: array-index-out-of-bounds in drivers/media/usb/dvb-usb-v2/az6007.c:821:30
> index 4096 is out of range for type 'unsigned char [4096]'
> CPU: 1 UID: 0 PID: 5832 Comm: syz-executor328 Not tainted 6.15.0-rc2-syzkaller-00493-gac71fabf1567 #0 PREEMPT(full)
> Call Trace:
>  <TASK>
>  az6007_i2c_xfer+0x549/0xc30 drivers/media/usb/dvb-usb-v2/az6007.c:821
>  i2c_transfer_buffer_flags+0x10c/0x190 drivers/i2c/i2c-core-base.c:2343
>  i2cdev_read+0x111/0x280 drivers/i2c/i2c-dev.c:155
>  do_loop_readv_writev fs/read_write.c:833 [inline]
>  do_preadv+0x1af/0x270 fs/read_write.c:1130
>  do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
> 
> Reported-by: syzbot+0192952caa411a3be209@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=0192952caa411a3be209
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
>  drivers/media/usb/dvb-usb-v2/az6007.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/usb/dvb-usb-v2/az6007.c b/drivers/media/usb/dvb-usb-v2/az6007.c
> index 65ef045b74ca..6322894eda27 100644
> --- a/drivers/media/usb/dvb-usb-v2/az6007.c
> +++ b/drivers/media/usb/dvb-usb-v2/az6007.c
> @@ -806,7 +806,8 @@ static int az6007_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msgs[],
>  			if (az6007_xfer_debug)
>  				printk(KERN_DEBUG "az6007: I2C R addr=0x%x len=%d\n",
>  				       addr, msgs[i].len);
> -			if (msgs[i].len < 1) {
> +			if (msgs[i].len < 1 ||
> +			    msgs[i].len > ARRAY_SIZE(st->data) - 5) {

Hmm, shouldn't this be '- 6'? Since a few lines below this the length passed
to __az6007_read is msgs[i].len + 6.

Regards,

	Hans

>  				ret = -EIO;
>  				goto err;
>  			}


  parent reply	other threads:[~2025-11-03 10:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  1:41 [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 13:40 ` syz test Arnaud Lecomte
2025-04-21 13:44   ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 13:43 ` Edward Adam Davis
2025-04-21 14:25   ` syzbot
2025-04-21 13:46 ` syz test Arnaud Lecomte
2025-04-21 14:58   ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:22 ` syz test Arnaud Lecomte
2025-04-21 16:12   ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:31 ` [PATCH] media: az6007: Add upper bound check to the data of device state Edward Adam Davis
2025-04-21 15:11   ` Arnaud Lecomte
2025-11-03 10:06   ` Hans Verkuil [this message]
2025-09-05 14:25 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer Jeongjun Park
2025-09-05 15:53   ` syzbot
2025-09-05 16:06 ` Jeongjun Park
2025-09-05 16:48   ` syzbot
2025-09-06  2:58 ` Jeongjun Park
2025-09-06  3:16   ` syzbot
2025-09-06  3:32 ` Jeongjun Park
2025-09-06  4:12   ` syzbot
2025-09-06  4:56 ` Jeongjun Park
2025-09-06  5:54   ` syzbot
2025-09-06 10:04 ` Jeongjun Park
2025-09-06 10:24   ` syzbot
2025-09-06 10:56 ` Jeongjun Park
2025-09-06 12:28   ` syzbot
2025-09-06 15:24 ` Jeongjun Park
2025-09-06 16:09   ` syzbot
2025-09-06 16:40 ` Jeongjun Park
2025-09-06 17:21   ` syzbot
2025-09-07  8:26 ` Jeongjun Park
2025-09-07  9:56   ` syzbot
2025-09-07 10:05 ` Jeongjun Park
2025-09-07 10:30   ` syzbot

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=d661ae00-d100-46ef-8a15-50919b34daae@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=syzbot+0192952caa411a3be209@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.