linux-kernel - [syzbot] [libertas?] [usb?] WARNING in usb_tx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <693f889b.a70a0220.104cf0.0333.GAE@google.com>
Date: Sun, 14 Dec 2025 20:03:39 -0800
From: syzbot <syzbot+67969ab6a2551c27f71b@...kaller.appspotmail.com>
To: libertas-dev@...ts.infradead.org, linux-kernel@...r.kernel.org, 
	linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org, 
	netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [libertas?] [usb?] WARNING in usb_tx_block

Hello,

syzbot found the following issue on:

HEAD commit:    d358e5254674 Merge tag 'for-6.19/dm-changes' of git://git...
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=116b511a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=53f37db573e619b
dashboard link: https://syzkaller.appspot.com/bug?extid=67969ab6a2551c27f71b
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=156b511a580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17278d92580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/584561f65dc7/disk-d358e525.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b9b8f5af8d1/vmlinux-d358e525.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2313fb12366/bzImage-d358e525.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67969ab6a2551c27f71b@...kaller.appspotmail.com

------------[ cut here ]------------
URB ffff888114e55c00 submitted while active
WARNING: drivers/usb/core/urb.c:380 at 0x0, CPU#0: kworker/0:1/10
Modules linked in:
CPU: 0 UID: 0 PID: 10 Comm: kworker/0:1 Not tainted syzkaller #0 PREEMPT(voluntary) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events request_firmware_work_func
RIP: 0010:usb_submit_urb+0x15a3/0x1970 drivers/usb/core/urb.c:380
Code: 4b 03 00 00 48 8b 04 24 48 8b 90 b0 00 00 00 eb 91 bb ed ff ff ff e9 07 f3 ff ff e8 97 f5 c5 fc 48 8d 3d 50 45 f0 05 48 89 de <67> 48 0f b9 3a bb f0 ff ff ff e9 e9 f2 ff ff e8 79 f5 c5 fc 0f 1f
RSP: 0018:ffffc900000af8d0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888114e55c00 RCX: ffffffff8427b986
RDX: ffff888101ab1d40 RSI: ffff888114e55c00 RDI: ffffffff8aaa3c30
RBP: ffff888114e55c00 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: ffff888101ab27e8 R12: 00000000c0030300
R13: 0000000000000010 R14: ffff888105a92000 R15: ffff88811ecda000
FS:  0000000000000000(0000) GS:ffff888268bf5000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056311e50a970 CR3: 0000000114500000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 usb_tx_block+0x241/0x2e0 drivers/net/wireless/marvell/libertas/if_usb.c:436
 if_usb_issue_boot_command drivers/net/wireless/marvell/libertas/if_usb.c:766 [inline]
 if_usb_prog_firmware+0x570/0x10c0 drivers/net/wireless/marvell/libertas/if_usb.c:859
 lbs_fw_loaded drivers/net/wireless/marvell/libertas/firmware.c:23 [inline]
 helper_firmware_cb drivers/net/wireless/marvell/libertas/firmware.c:80 [inline]
 helper_firmware_cb+0x1f8/0x2e0 drivers/net/wireless/marvell/libertas/firmware.c:64
 request_firmware_work_func+0x13c/0x250 drivers/base/firmware_loader/main.c:1152
 process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257
 process_scheduled_works kernel/workqueue.c:3340 [inline]
 worker_thread+0x6c8/0xf10 kernel/workqueue.c:3421
 kthread+0x3c5/0x780 kernel/kthread.c:463
 ret_from_fork+0x74f/0xa30 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
----------------
Code disassembly (best guess):
   0:	4b 03 00             	rex.WXB add (%r8),%rax
   3:	00 48 8b             	add    %cl,-0x75(%rax)
   6:	04 24                	add    $0x24,%al
   8:	48 8b 90 b0 00 00 00 	mov    0xb0(%rax),%rdx
   f:	eb 91                	jmp    0xffffffa2
  11:	bb ed ff ff ff       	mov    $0xffffffed,%ebx
  16:	e9 07 f3 ff ff       	jmp    0xfffff322
  1b:	e8 97 f5 c5 fc       	call   0xfcc5f5b7
  20:	48 8d 3d 50 45 f0 05 	lea    0x5f04550(%rip),%rdi        # 0x5f04577
  27:	48 89 de             	mov    %rbx,%rsi
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	bb f0 ff ff ff       	mov    $0xfffffff0,%ebx
  34:	e9 e9 f2 ff ff       	jmp    0xfffff322
  39:	e8 79 f5 c5 fc       	call   0xfcc5f5b7
  3e:	0f                   	.byte 0xf
  3f:	1f                   	(bad)


---
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@...glegroups.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 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.

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