[v5.15] WARNING in dib0700_i2c_xfer/usb_submit_urb

3 views
Skip to first unread message

syzbot

unread,
Aug 6, 2025, 7:36:31 PM8/6/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1429d6a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=4ae72cdc1d53ecb1f5f8
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4ae72c...@syzkaller.appspotmail.com

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 4356 at drivers/usb/core/urb.c:412 usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 1 PID: 4356 Comm: syz.1.32 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Code: ff df 0f b6 44 05 00 84 c0 0f 85 7d 06 00 00 45 0f b6 07 48 c7 c7 a0 50 a4 8a 48 8b 74 24 30 4c 89 e2 44 89 f1 e8 a0 3b cf 03 <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 3b f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc900034ef868 EFLAGS: 00010246
RAX: aa03e48ff228df00 RBX: ffff8880193fd000 RCX: 0000000000080000
RDX: ffffc90004c9a000 RSI: 000000000001c19d RDI: 000000000001c19e
RBP: 1ffff1100ba1078b R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: ffff888144bd8c30
R13: dffffc0000000000 R14: 0000000080000280 R15: ffff88805d083c58
FS: 00007f3b150e46c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055677a30d660 CR3: 000000001b690000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x111/0x4b0 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x22f/0x3e0 drivers/usb/core/message.c:153
dib0700_ctrl_rd drivers/media/usb/dvb-usb/dib0700_core.c:95 [inline]
dib0700_i2c_xfer_legacy drivers/media/usb/dvb-usb/dib0700_core.c:315 [inline]
dib0700_i2c_xfer+0xbbd/0xf80 drivers/media/usb/dvb-usb/dib0700_core.c:361
__i2c_transfer+0x864/0x2060 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2330
i2cdev_ioctl_rdwr+0x3da/0x6c0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x5ba/0x750 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3b16e7cbe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3b150e4038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f3b170a3fa0 RCX: 00007f3b16e7cbe9
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f3b16effe19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3b170a4038 R14: 00007f3b170a3fa0 R15: 00007ffe30d183a8
</TASK>


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Aug 9, 2025, 12:28:33 AM8/9/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15f3c1a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=4ae72cdc1d53ecb1f5f8
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13bf9434580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168de1a2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4ae72c...@syzkaller.appspotmail.com

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 4344 at drivers/usb/core/urb.c:412 usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 0 PID: 4344 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Code: ff df 0f b6 44 05 00 84 c0 0f 85 7d 06 00 00 45 0f b6 07 48 c7 c7 a0 50 a4 8a 48 8b 74 24 30 4c 89 e2 44 89 f1 e8 a0 3b cf 03 <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 3b f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc90002327868 EFLAGS: 00010246
RAX: 36c65be77447d700 RBX: ffff888022352100 RCX: ffff888020d95940
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffff1100583dbd1 R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: ffff888141decc30
R13: dffffc0000000000 R14: 0000000080000280 R15: ffff88802c1ede88
FS: 000055556ea4e500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005577d1a5cea8 CR3: 0000000072b8f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x111/0x4b0 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x22f/0x3e0 drivers/usb/core/message.c:153
dib0700_ctrl_rd drivers/media/usb/dvb-usb/dib0700_core.c:95 [inline]
dib0700_i2c_xfer_legacy drivers/media/usb/dvb-usb/dib0700_core.c:315 [inline]
dib0700_i2c_xfer+0xbbd/0xf80 drivers/media/usb/dvb-usb/dib0700_core.c:361
__i2c_transfer+0x864/0x2060 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2330
i2cdev_ioctl_rdwr+0x3da/0x6c0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x5ba/0x750 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8736ca7be9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd79ab7008 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8736ecefa0 RCX: 00007f8736ca7be9
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f8736d2ae19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8736ecefa0 R14: 00007f8736ecefa0 R15: 0000000000000003
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages