[moderation] [sound?] BUG: corrupted list in snd_card_file_remove

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=159b16df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=86dd15278dbfe19f
dashboard link: https://syzkaller.appspot.com/bug?extid=8a539aa363ff41c1d3a0
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org linux...@vger.kernel.org pe...@perex.cz ti...@suse.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d24eb225cff7/disk-ccb98cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd81532f8240/vmlinux-ccb98cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18b08e4bbf40/bzImage-ccb98cce.xz

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

list_del corruption. next->prev should be ffff88802f06e920, but was 0000000000000000. (next=ffff88801eb2aaa0)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:65!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 7523 Comm: syz.3.375 Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__list_del_entry_valid_or_report+0x141/0x1c0 lib/list_debug.c:65
Code: db fc 90 0f 0b 48 89 c2 48 c7 c7 60 75 b1 8b e8 15 06 db fc 90 0f 0b 48 89 d1 48 c7 c7 e0 75 b1 8b 48 89 c2 e8 00 06 db fc 90 <0f> 0b 48 89 34 24 e8 54 f9 5d fd 48 8b 34 24 e9 d5 fe ff ff 48 89
RSP: 0018:ffffc900041cfd50 EFLAGS: 00010286
RAX: 000000000000006d RBX: ffff88802f06e900 RCX: ffffffff8178e2b9
RDX: 0000000000000000 RSI: ffffffff81798a46 RDI: 0000000000000005
RBP: ffff88802f06e920 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: dffffc0000000000
R13: ffff88814d7c43a8 R14: ffff888031354fc0 R15: ffff88814d7c4028
FS: 0000555557081500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc7009626a0 CR3: 00000000633c2000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_del include/linux/list.h:229 [inline]
snd_card_file_remove+0xc7/0x5d0 sound/core/init.c:1102
snd_pcm_oss_release+0x217/0x310 sound/core/oss/pcm_oss.c:2581
__fput+0x3f8/0xb60 fs/file_table.c:450
task_work_run+0x14e/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x27b/0x2a0 kernel/entry/common.c:218
do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1dce785d29
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:00007fff9a6bbf08 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000026b07 RCX: 00007f1dce785d29
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f1dce977ba0 R08: 0000000000000001 R09: 00007fff9a6bc1ff
R10: 00007f1dce600000 R11: 0000000000000246 R12: 0000000000026b85
R13: 00007f1dce975fa0 R14: 0000000000000032 R15: ffffffffffffffff
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x141/0x1c0 lib/list_debug.c:65
Code: db fc 90 0f 0b 48 89 c2 48 c7 c7 60 75 b1 8b e8 15 06 db fc 90 0f 0b 48 89 d1 48 c7 c7 e0 75 b1 8b 48 89 c2 e8 00 06 db fc 90 <0f> 0b 48 89 34 24 e8 54 f9 5d fd 48 8b 34 24 e9 d5 fe ff ff 48 89
RSP: 0018:ffffc900041cfd50 EFLAGS: 00010286
RAX: 000000000000006d RBX: ffff88802f06e900 RCX: ffffffff8178e2b9
RDX: 0000000000000000 RSI: ffffffff81798a46 RDI: 0000000000000005
RBP: ffff88802f06e920 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: dffffc0000000000
R13: ffff88814d7c43a8 R14: ffff888031354fc0 R15: ffff88814d7c4028
FS: 0000555557081500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc7009626a0 CR3: 00000000633c2000 CR4: 00000000003526f0
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