All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+427909a2e3b2f83d78cb@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	 linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in ADDR_ctrl_msg/usb_submit_urb
Date: Sun, 04 Jan 2026 11:19:29 -0800	[thread overview]
Message-ID: <695abd41.050a0220.a1b6.0392.GAE@google.com> (raw)
In-Reply-To: <69322f1d.a70a0220.d98e3.01e2.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    cc3aa43b44bd Add linux-next specific files for 20251219
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1336269a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=da1bc82c6189c463
dashboard link: https://syzkaller.appspot.com/bug?extid=427909a2e3b2f83d78cb
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11698074580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1736269a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/30bf539e6f28/disk-cc3aa43b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0e2f8b08e342/vmlinux-cc3aa43b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ec7ee6ece11f/bzImage-cc3aa43b.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: drivers/usb/core/urb.c:414 at usb_submit_urb+0x105c/0x18d0 drivers/usb/core/urb.c:412, CPU#0: syz.0.17/6000
Modules linked in:
CPU: 0 UID: 0 PID: 6000 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:usb_submit_urb+0x111c/0x18d0 drivers/usb/core/urb.c:412
Code: b8 00 00 00 00 00 fc ff df 0f b6 44 05 00 84 c0 0f 85 a7 05 00 00 45 0f b6 45 00 48 8b 3c 24 48 8b 74 24 20 4c 89 fa 44 89 f1 <67> 48 0f b9 3a 49 bf 00 00 00 00 00 fc ff df e9 b7 f2 ff ff 89 e9
RSP: 0018:ffffc9000ecf7760 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888032177a00 RCX: 0000000080000280
RDX: ffff8880203d1e80 RSI: ffffffff8c341f40 RDI: ffffffff8faef860
RBP: 1ffff110283df6ec R08: 00000000000000c0 R09: 0000000000000000
R10: ffffc9000ecf7860 R11: fffff52001d9ef18 R12: ffff8881426d1100
R13: ffff888141efb760 R14: 0000000080000280 R15: ffff8880203d1e80
FS:  0000555584472500(0000) GS:ffff888125c25000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30663fff CR3: 00000000762fe000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 usb_start_wait_urb+0x115/0x4f0 drivers/usb/core/message.c:59
 usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
 usb_control_msg+0x232/0x3e0 drivers/usb/core/message.c:154
 ce6230_ctrl_msg+0x2b1/0x660 drivers/media/usb/dvb-usb-v2/ce6230.c:61
 ce6230_i2c_master_xfer+0x4ce/0x6d0 drivers/media/usb/dvb-usb-v2/ce6230.c:113
 __i2c_transfer+0x871/0x2110 drivers/i2c/i2c-core-base.c:-1
 i2c_transfer+0x25b/0x3a0 drivers/i2c/i2c-core-base.c:2317
 i2cdev_ioctl_rdwr+0x460/0x740 drivers/i2c/i2c-dev.c:306
 i2cdev_ioctl+0x64b/0x820 drivers/i2c/i2c-dev.c:467
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f10c3b8f749
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:00007ffe182be228 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f10c3de5fa0 RCX: 00007f10c3b8f749
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f10c3c13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f10c3de5fa0 R14: 00007f10c3de5fa0 R15: 0000000000000003
 </TASK>
----------------
Code disassembly (best guess):
   0:	b8 00 00 00 00       	mov    $0x0,%eax
   5:	00 fc                	add    %bh,%ah
   7:	ff                   	(bad)
   8:	df 0f                	fisttps (%rdi)
   a:	b6 44                	mov    $0x44,%dh
   c:	05 00 84 c0 0f       	add    $0xfc08400,%eax
  11:	85 a7 05 00 00 45    	test   %esp,0x45000005(%rdi)
  17:	0f b6 45 00          	movzbl 0x0(%rbp),%eax
  1b:	48 8b 3c 24          	mov    (%rsp),%rdi
  1f:	48 8b 74 24 20       	mov    0x20(%rsp),%rsi
  24:	4c 89 fa             	mov    %r15,%rdx
  27:	44 89 f1             	mov    %r14d,%ecx
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	49 bf 00 00 00 00 00 	movabs $0xdffffc0000000000,%r15
  36:	fc ff df
  39:	e9 b7 f2 ff ff       	jmp    0xfffff2f5
  3e:	89 e9                	mov    %ebp,%ecx


---
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	other threads:[~2026-01-04 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  1:02 [syzbot] [usb?] WARNING in ADDR_ctrl_msg/usb_submit_urb syzbot
2026-01-04 19:19 ` syzbot [this message]
2026-04-22 18:50 ` Forwarded: [PATCH 1/1] media: dvb-usb-v2: ce6230: fix bug when sending usb_control_msg of size 0 syzbot
     [not found] <20260422185001.1584-2-jakovnovak30@gmail.com>
2026-04-22 19:24 ` [syzbot] [usb?] WARNING in ADDR_ctrl_msg/usb_submit_urb 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=695abd41.050a0220.a1b6.0392.GAE@google.com \
    --to=syzbot+427909a2e3b2f83d78cb@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 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.