From: syzbot <syzbot+7dbcd9ff34dc4ed45240@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, johan@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mathias.nyman@linux.intel.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in usb_new_device/usb_submit_urb
Date: Wed, 02 Jun 2021 16:30:18 -0700 [thread overview]
Message-ID: <00000000000075c23d05c3d0d730@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 7652dd2c USB: core: Check buffer length matches wLength fo..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=1712b99dd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=1206ee92dd3d988d
dashboard link: https://syzkaller.appspot.com/bug?extid=7dbcd9ff34dc4ed45240
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b82e13d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ac418dd00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7dbcd9ff34dc4ed45240@syzkaller.appspotmail.com
usb 1-1: config 0 interface 186 altsetting 4 has a duplicate endpoint with address 0x8, skipping
usb 1-1: config 0 interface 166 has no altsetting 0
usb 1-1: config 0 interface 186 has no altsetting 0
------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType 80
WARNING: CPU: 1 PID: 2632 at drivers/usb/core/urb.c:410 usb_submit_urb+0x149d/0x18a0 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 1 PID: 2632 Comm: kworker/1:2 Not tainted 5.13.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: usb_hub_wq hub_event
RIP: 0010:usb_submit_urb+0x149d/0x18a0 drivers/usb/core/urb.c:410
Code: 7c 24 40 e8 c5 1f b3 fd 48 8b 7c 24 40 e8 6b a6 1b ff 45 89 e8 44 89 f1 4c 89 e2 48 89 c6 48 c7 c7 80 0a 63 86 e8 15 ec fb 01 <0f> 0b e9 a5 ee ff ff e8 97 1f b3 fd 0f b6 1d db a7 34 05 31 ff 41
RSP: 0018:ffffc90000207680 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8881182df058 RCX: 0000000000000000
RDX: ffff888114871b40 RSI: ffffffff812a6033 RDI: fffff52000040ec2
RBP: ffff88810cfffc80 R08: 0000000000000001 R09: 0000000000000000
R10: ffffffff814b998b R11: 0000000000000000 R12: ffff88810cfff6b8
R13: 0000000000000080 R14: 0000000080000280 R15: ffff88810e736f00
FS: 0000000000000000(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13a00114f0 CR3: 0000000108807000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
usb_start_wait_urb+0x101/0x4c0 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x31c/0x4a0 drivers/usb/core/message.c:153
usb_get_string+0xa6/0x190 drivers/usb/core/message.c:837
usb_string_sub+0x35e/0x3d0 drivers/usb/core/message.c:883
usb_get_langid drivers/usb/core/message.c:913 [inline]
usb_string+0x1cc/0x540 drivers/usb/core/message.c:977
usb_cache_string+0x82/0x120 drivers/usb/core/message.c:1023
usb_enumerate_device drivers/usb/core/hub.c:2399 [inline]
usb_new_device+0x15b/0x7d0 drivers/usb/core/hub.c:2527
hub_port_connect drivers/usb/core/hub.c:5298 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5438 [inline]
port_event drivers/usb/core/hub.c:5584 [inline]
hub_event+0x2357/0x4330 drivers/usb/core/hub.c:5666
process_one_work+0x98d/0x1580 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x38c/0x460 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2021-06-02 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 23:30 syzbot [this message]
2021-06-03 1:43 ` [syzbot] WARNING in usb_new_device/usb_submit_urb Alan Stern
2021-06-03 2:45 ` syzbot
2021-06-04 16:10 ` [PATCH] USB: core: Avoid WARNings for 0-length descriptor requests Alan Stern
2021-06-07 2:31 ` Peter Chen
2021-06-07 7:57 ` Johan Hovold
2021-06-07 15:23 ` [PATCH v2] " Alan Stern
2021-06-07 15:26 ` Johan Hovold
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=00000000000075c23d05c3d0d730@google.com \
--to=syzbot+7dbcd9ff34dc4ed45240@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.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.