[v6.1] WARNING in sock_map_destroy

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fdb6fcb41cc7 Linux 6.1.176
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111a0689580000
kernel config: https://syzkaller.appspot.com/x/.config?x=acfbe65fbce84c0c
dashboard link: https://syzkaller.appspot.com/bug?extid=c2101220db4c291f8fc5
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1609e67fe610/disk-fdb6fcb4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7c9914a35256/vmlinux-fdb6fcb4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/401dd54d7ec6/bzImage-fdb6fcb4.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 6803 at net/core/sock_map.c:1614 sock_map_destroy+0x27c/0x2a0 net/core/sock_map.c:1614
Modules linked in:
CPU: 1 PID: 6803 Comm: syz.5.610 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:sock_map_destroy+0x27c/0x2a0 net/core/sock_map.c:1614
Code: 2c 8d f9 4d 8b 36 49 83 c6 38 4c 89 f0 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 f7 e8 3e 2c 8d f9 4d 8b 2e eb 85 e8 74 04 3c f9 <0f> 0b eb a6 e8 6b 04 3c f9 4c 89 ff be 03 00 00 00 e8 ee cc c9 fb
RSP: 0018:ffffc9000c5ffc00 EFLAGS: 00010293
RAX: ffffffff88461c9c RBX: ffff888073ff6600 RCX: ffff888065c35a00
RDX: 0000000000000000 RSI: ffffffff8a8c2920 RDI: ffffffff8adee1a0
RBP: 0000000000000001 R08: ffffffff8e200f6f R09: 1ffffffff1c401ed
R10: dffffc0000000000 R11: fffffbfff1c401ee R12: ffff888073ff6698
R13: ffffffff88461a20 R14: ffffffff970391f8 R15: ffffffff970391f8
FS: 000055556d487500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e21effc CR3: 0000000078817000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inet_csk_destroy_sock+0x15c/0x350 net/ipv4/inet_connection_sock.c:1229
__tcp_close+0xb04/0xdd0 net/ipv4/tcp.c:3070
tcp_close+0x24/0x110 net/ipv4/tcp.c:3082
inet_release+0x139/0x180 net/ipv4/af_inet.c:430
__sock_release net/socket.c:654 [inline]
sock_close+0xbf/0x210 net/socket.c:1400
__fput+0x20a/0x8b0 fs/file_table.c:320
task_work_run+0x1d0/0x260 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7faef3d9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3a710988 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fff3a710a70 RCX: 00007faef3d9ce59
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000032f84 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b2d020000 R11: 0000000000000246 R12: 00007fff3a710ab0
R13: 00007faef401609c R14: 000000000003302f R15: 00007faef4016090
</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 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