linux-kernel - [syzbot] [pvrusb2?] WARNING in pvr2_send_request/usb_submit

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: <6897b6b5.050a0220.7f033.00b2.GAE@google.com>
Date: Sat, 09 Aug 2025 13:59:33 -0700
From: syzbot <syzbot+1237a720b657b1d06a22@...kaller.appspotmail.com>
To: isely@...ox.com, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, 
	linux-usb@...r.kernel.org, mchehab@...nel.org, pvrusb2@...ly.net, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [pvrusb2?] WARNING in pvr2_send_request/usb_submit_urb

Hello,

syzbot found the following issue on:

HEAD commit:    d632ab86aff2 Merge tag 'for-6.17/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=137422f0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6f764ce607e41bad
dashboard link: https://syzkaller.appspot.com/bug?extid=1237a720b657b1d06a22
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f6912b7acf0b/disk-d632ab86.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ddc035c67711/vmlinux-d632ab86.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a995ca981cbf/bzImage-d632ab86.xz

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

WARNING: CPU: 0 PID: 1309 at drivers/usb/core/urb.c:379 usb_submit_urb+0x1519/0x1770 drivers/usb/core/urb.c:379
Modules linked in:
CPU: 0 UID: 0 PID: 1309 Comm: pvrusb2-context Not tainted 6.16.0-syzkaller-11568-gd632ab86aff2 #0 PREEMPT(voluntary) 
RIP: 0010:usb_submit_urb+0x1519/0x1770 drivers/usb/core/urb.c:379
Code: fd eb cb bb fe ff ff ff e9 96 f3 ff ff e8 5f 38 da fc c6 05 ac 36 cb 05 01 90 48 c7 c7 80 71 c5 87 48 89 de e8 b8 f2 9c fc 90 <0f> 0b 90 90 e9 ac fe ff ff bb f8 ff ff ff e9 66 f3 ff ff 48 89 ef
RSP: 0018:ffffc90001cbeda8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88810cf23300 RCX: ffffffff8140b968
RDX: ffff88811193ba00 RSI: ffffffff8140b975 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000
R13: 00000000c000a800 R14: ffff888137f6e000 R15: ffff888136599610
FS:  0000000000000000(0000) GS:ffff88826911d000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faf709fae9c CR3: 0000000123a8c000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 pvr2_send_request+0x3a/0x50 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:3819
 pvr2_i2c_read+0x203/0x6d0 drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c:130
 pvr2_i2c_basic_op+0xcf/0xf0 drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c:172
 pvr2_i2c_xfer+0x37d/0xfd0 drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c:445
 __i2c_transfer+0x6b3/0x2190 drivers/i2c/i2c-core-base.c:2264
 i2c_smbus_xfer_emulated+0x230/0x11f0 drivers/i2c/i2c-core-smbus.c:470
 __i2c_smbus_xfer drivers/i2c/i2c-core-smbus.c:608 [inline]
 __i2c_smbus_xfer+0x836/0x1020 drivers/i2c/i2c-core-smbus.c:554
 i2c_smbus_xfer drivers/i2c/i2c-core-smbus.c:546 [inline]
 i2c_smbus_xfer+0x200/0x3c0 drivers/i2c/i2c-core-smbus.c:536
 i2c_smbus_read_byte_data+0x135/0x1e0 drivers/i2c/i2c-core-smbus.c:143
 saa711x_detect_chip drivers/media/i2c/saa7115.c:1710 [inline]
 saa711x_probe+0x234/0x20b0 drivers/media/i2c/saa7115.c:1816
 i2c_device_probe+0x65d/0xd40 drivers/i2c/i2c-core-base.c:591
 call_driver_probe drivers/base/dd.c:581 [inline]
 really_probe+0x23e/0xa90 drivers/base/dd.c:659
 __driver_probe_device+0x1de/0x440 drivers/base/dd.c:801
 driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:831
 __device_attach_driver+0x1df/0x310 drivers/base/dd.c:959
 bus_for_each_drv+0x156/0x1e0 drivers/base/bus.c:462
 __device_attach+0x1e4/0x4b0 drivers/base/dd.c:1031
 bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:537
 device_add+0x1148/0x1aa0 drivers/base/core.c:3689
 i2c_new_client_device+0x660/0xeb0 drivers/i2c/i2c-core-base.c:1022
 v4l2_i2c_new_subdev_board+0xb6/0x300 drivers/media/v4l2-core/v4l2-i2c.c:81
 v4l2_i2c_new_subdev+0x14f/0x1c0 drivers/media/v4l2-core/v4l2-i2c.c:136
 pvr2_hdw_load_subdev drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2022 [inline]
 pvr2_hdw_load_modules drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2074 [inline]
 pvr2_hdw_setup_low drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2155 [inline]
 pvr2_hdw_setup drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2261 [inline]
 pvr2_hdw_initialize+0x28d0/0x4510 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2338
 pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:111 [inline]
 pvr2_context_thread_func+0x253/0x9b0 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
 kthread+0x3c5/0x780 kernel/kthread.c:463
 ret_from_fork+0x5b6/0x6c0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </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 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 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