[syzbot] [net?] WARNING in tcp_disconnect (2)

[syzbot <syzbot+0f423d4ae07bbb1359ac@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    ff63cc2e9506 net: phy: mediatek-ge-soc: sync driver with M..
git tree:       bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=133ee64be80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bc36d99546fe9035
dashboard link: https://syzkaller.appspot.com/bug?extid=0f423d4ae07bbb1359ac
compiler:       gcc (Debian 12.2.0-14) 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/09601b75d815/disk-ff63cc2e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a5549b0aa031/vmlinux-ff63cc2e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1eb3b2eb752/bzImage-ff63cc2e.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 26544 at net/ipv4/tcp.c:3089 tcp_disconnect+0x1857/0x1df0 net/ipv4/tcp.c:3089
Modules linked in:
CPU: 1 PID: 26544 Comm: syz-executor.2 Not tainted 6.8.0-rc1-syzkaller-00182-gff63cc2e9506 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:tcp_disconnect+0x1857/0x1df0 net/ipv4/tcp.c:3089
Code: 00 00 48 89 04 24 e9 24 e9 ff ff e8 13 fb 84 f8 be 07 00 00 00 bf 02 00 00 00 e8 74 f6 84 f8 e9 0b e9 ff ff e8 fa fa 84 f8 90 <0f> 0b 90 e9 21 fa ff ff e8 ec fa 84 f8 4d 8d af 76 08 00 00 4c 89
RSP: 0018:ffffc9000371f7c0 EFLAGS: 00010246
RAX: 0000000000040000 RBX: 000000000000d038 RCX: ffffc9000b6ed000
RDX: 0000000000040000 RSI: ffffffff890328c6 RDI: ffff888043389f18
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
R10: 000000000000d038 R11: 0000000000000002 R12: ffff88801c9a0600
R13: ffff88804338a0f6 R14: ffff888043389a38 R15: ffff888043389880
FS:  00007fee2d7bc6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f075e6d56c6 CR3: 000000003fa89000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __mptcp_subflow_disconnect net/mptcp/protocol.c:2366 [inline]
 __mptcp_close_ssk+0xb26/0xfd0 net/mptcp/protocol.c:2420
 mptcp_destroy_common+0x168/0x650 net/mptcp/protocol.c:3274
 mptcp_disconnect+0x22c/0x810 net/mptcp/protocol.c:3145
 mptcp_sendmsg_fastopen net/mptcp/protocol.c:1745 [inline]
 mptcp_sendmsg+0x15ec/0x1b20 net/mptcp/protocol.c:1782
 inet_sendmsg+0x9d/0xe0 net/ipv4/af_inet.c:850
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg+0xd5/0x180 net/socket.c:745
 ____sys_sendmsg+0x6ac/0x940 net/socket.c:2584
 ___sys_sendmsg+0x135/0x1d0 net/socket.c:2638
 __sys_sendmsg+0x117/0x1e0 net/socket.c:2667
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fee2ca7cda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fee2d7bc0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fee2cbabf80 RCX: 00007fee2ca7cda9
RDX: 0000000024000084 RSI: 0000000020000340 RDI: 0000000000000003
RBP: 00007fee2d7bc120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007fee2cbabf80 R15: 00007ffd6be957c8
 </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@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