The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+0cd0fb4cf3f4722d6663@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [usb?] WARNING in dib0700_ctrl_rd/usb_submit_urb
Date: Sat, 20 Jun 2026 22:33:50 -0700	[thread overview]
Message-ID: <6a3777be.c19584c1.44bb3.0006.GAE@google.com> (raw)
In-Reply-To: <6854cfb9.a00a0220.137b3.0028.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [usb?] WARNING in dib0700_ctrl_rd/usb_submit_urb
Author: contact@henrialfonso.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 9afe652958c3

diff --git a/drivers/media/usb/dvb-usb/dib0700_core.c b/drivers/media/usb/dvb-usb/dib0700_core.c
  index 986e552f0a97..000000000000 100644
  @@ -311,6 +311,11 @@ static int dib0700_i2c_xfer_legacy(struct i2c_adapter *adap,
                        st->buf[0] = REQUEST_I2C_READ;
                        st->buf[1] |= 1;

  +                     if (msg[i + 1].len == 0) {
  +                             result = -EINVAL;
  +                             goto unlock;
  +                     }
  +
                        /* special thing in the current firmware: when length is zero the read-failed */
                        len = dib0700_ctrl_rd(d, st->buf, msg[i].len + 2,
                                              st->buf, msg[i + 1].len);

  reply	other threads:[~2026-06-21  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  3:04 [syzbot] [usb?] WARNING in dib0700_ctrl_rd/usb_submit_urb syzbot
2026-06-21  5:33 ` syzbot [this message]
2026-06-21 13:56 ` Forwarded: " syzbot
2026-06-21 15:32 ` syzbot
2026-06-21 15:48 ` syzbot
2026-06-21 16:51 ` 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=6a3777be.c19584c1.44bb3.0006.GAE@google.com \
    --to=syzbot+0cd0fb4cf3f4722d6663@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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