[v5.15] BUG: corrupted list in az6007_i2c_xfer

[syzbot]

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=109726f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=dbaa418de6f55c5371cc
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+dbaa41...@syzkaller.appspotmail.com

list_del corruption. prev->next should be ffffc9000334fa20, but was ffff88802601c050
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4484 Comm: syz.2.71 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__list_del_entry_valid+0x107/0x120 lib/list_debug.c:59
Code: 48 89 de e8 0b 01 bf 05 0f 0b 48 c7 c7 80 97 59 8a 48 89 de e8 fa 00 bf 05 0f 0b 48 c7 c7 e0 97 59 8a 48 89 de e8 e9 00 bf 05 <0f> 0b 48 c7 c7 40 98 59 8a 48 89 de e8 d8 00 bf 05 0f 0b 00 00 cc
RSP: 0018:ffffc9000334f918 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffffc9000334fa20 RCX: 45004007ae65ec00
RDX: ffffc9000ced1000 RSI: 0000000000004fbc RDI: 0000000000004fbd
RBP: ffffc9000334fad0 R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88802601c050 R15: ffff88802601c050
FS: 00007f97937e36c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32719ff8 CR3: 000000005ef1e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:132 [inline]
list_del include/linux/list.h:146 [inline]
__mutex_remove_waiter kernel/locking/mutex.c:212 [inline]
__mutex_lock_common+0x1211/0x2390 kernel/locking/mutex.c:699
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_interruptible_nested+0x17/0x20 kernel/locking/mutex.c:765
az6007_i2c_xfer+0x82/0x1320 drivers/media/usb/dvb-usb-v2/az6007.c:755
__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:0x7f979557bbe9
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:00007f97937e3038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f97957a2fa0 RCX: 00007f979557bbe9
RDX: 00002000000001c0 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f97955fee19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f97957a3038 R14: 00007f97957a2fa0 R15: 00007fff4bcdea98
</TASK>
Modules linked in:
---[ end trace cd2f0d5eae0648ba ]---
RIP: 0010:__list_del_entry_valid+0x107/0x120 lib/list_debug.c:59
Code: 48 89 de e8 0b 01 bf 05 0f 0b 48 c7 c7 80 97 59 8a 48 89 de e8 fa 00 bf 05 0f 0b 48 c7 c7 e0 97 59 8a 48 89 de e8 e9 00 bf 05 <0f> 0b 48 c7 c7 40 98 59 8a 48 89 de e8 d8 00 bf 05 0f 0b 00 00 cc
RSP: 0018:ffffc9000334f918 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffffc9000334fa20 RCX: 45004007ae65ec00
RDX: ffffc9000ced1000 RSI: 0000000000004fbc RDI: 0000000000004fbd
RBP: ffffc9000334fad0 R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88802601c050 R15: ffff88802601c050
FS: 00007f97937e36c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32719ff8 CR3: 000000005ef1e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.