Hello,
syzbot found the following issue on:
HEAD commit: 355bd0b51d2f Linux 6.6.104
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=13021562580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=dac93b93d3de2741
dashboard link:
https://syzkaller.appspot.com/bug?extid=e5ff5368d9fa2f9e6c55
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/ef00d28b2c5b/disk-355bd0b5.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/7627cd51eb0a/vmlinux-355bd0b5.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3fdd0a51dd65/bzImage-355bd0b5.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e5ff53...@syzkaller.appspotmail.com
dvb-usb: bulk message failed: -22 (1/0)
dw2102: i2c transfer failed.
general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
CPU: 0 PID: 8241 Comm: syz.2.607 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:su3000_i2c_transfer+0x2e3/0x1020 drivers/media/usb/dvb-usb/dw2102.c:749
Code: 0f b6 18 49 83 c7 08 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 ff e8 6a 85 d8 fa 4d 8b 37 49 ff c6 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 d7 08 00 00 41 88 1e 48 8b 44 24 48 42
RSP: 0018:ffffc900196d7ac8 EFLAGS: 00010202
RAX: 0000000000000002 RBX: 0000000000000010 RCX: 328766c108f21100
RDX: ffffc9000d113000 RSI: 00000000000039d6 RDI: 00000000000039d7
RBP: 0000000000000000 R08: ffffc900196d76c7 R09: 1ffff920032daed8
R10: dffffc0000000000 R11: fffff520032daed9 R12: 0000000000000001
R13: dffffc0000000000 R14: 0000000000000011 R15: ffff88805bf7be68
FS: 00007ff94bff66c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ea23ffc CR3: 000000002fcfe000 CR4: 00000000003506f0
Call Trace:
<TASK>
__i2c_transfer+0x868/0x2080 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x250/0x390 drivers/i2c/i2c-core-base.c:2328
i2cdev_ioctl_rdwr+0x3b0/0x690 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x646/0x7e0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff94dd8ebe9
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:00007ff94bff6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff94dfc5fa0 RCX: 00007ff94dd8ebe9
RDX: 0000200000000080 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007ff94de11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff94dfc6038 R14: 00007ff94dfc5fa0 R15: 00007ffd04534ff8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:su3000_i2c_transfer+0x2e3/0x1020 drivers/media/usb/dvb-usb/dw2102.c:749
Code: 0f b6 18 49 83 c7 08 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 ff e8 6a 85 d8 fa 4d 8b 37 49 ff c6 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 d7 08 00 00 41 88 1e 48 8b 44 24 48 42
RSP: 0018:ffffc900196d7ac8 EFLAGS: 00010202
RAX: 0000000000000002 RBX: 0000000000000010 RCX: 328766c108f21100
RDX: ffffc9000d113000 RSI: 00000000000039d6 RDI: 00000000000039d7
RBP: 0000000000000000 R08: ffffc900196d76c7 R09: 1ffff920032daed8
R10: dffffc0000000000 R11: fffff520032daed9 R12: 0000000000000001
R13: dffffc0000000000 R14: 0000000000000011 R15: ffff88805bf7be68
FS: 00007ff94bff66c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbc17994198 CR3: 000000002fcfe000 CR4: 00000000003506f0
----------------
Code disassembly (best guess):
0: 0f b6 18 movzbl (%rax),%ebx
3: 49 83 c7 08 add $0x8,%r15
7: 4c 89 f8 mov %r15,%rax
a: 48 c1 e8 03 shr $0x3,%rax
e: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1)
13: 74 08 je 0x1d
15: 4c 89 ff mov %r15,%rdi
18: e8 6a 85 d8 fa call 0xfad88587
1d: 4d 8b 37 mov (%r15),%r14
20: 49 ff c6 inc %r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 d7 08 00 00 jne 0x90e
37: 41 88 1e mov %bl,(%r14)
3a: 48 8b 44 24 48 mov 0x48(%rsp),%rax
3f: 42 rex.X
---
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