[v6.1] WARNING in inet_csk_get_port (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16100332580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=e4f0060517655d9cd5fd
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4459 at net/ipv4/inet_connection_sock.c:590 inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
Modules linked in:
CPU: 0 PID: 4459 Comm: syz.0.10 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
lr : inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
sp : ffff800021637b30
x29: ffff800021637c20 x28: ffff0000d83ed000 x27: dfff800000000000
x26: ffff0000d71b6fa8 x25: 0000000000004e20 x24: dfff800000000000
x23: ffff80001c751ee0 x22: ffff0000d8bfd080 x21: 1fffe0001ac85636
x20: ffff0000d642b1b0 x19: ffff0000d642b1b8 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082d25ac x15: 0000000000000002
x14: 00000000ffff0000 x13: 1ffff00002a180b1 x12: 0000000000080000
x11: 000000000000060a x10: ffff800022769000 x9 : ffff80001043b098
x8 : 000000000000060b x7 : ffff80000fcd3298 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000002 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
inet_csk_listen_start+0x104/0x2c4 net/ipv4/inet_connection_sock.c:1296
inet_dccp_listen+0x194/0x260 net/dccp/proto.c:948
__sys_listen+0x198/0x21c net/socket.c:1845
__do_sys_listen net/socket.c:1854 [inline]
__se_sys_listen net/socket.c:1852 [inline]
__arm64_sys_listen+0x5c/0x74 net/socket.c:1852
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 833
hardirqs last enabled at (832): [<ffff8000081a8850>] __local_bh_enable_ip+0x1f8/0x380 kernel/softirq.c:426
hardirqs last disabled at (833): [<ffff80001195cc30>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (818): [<ffff80000fcd9324>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (818): [<ffff80000fcd9324>] lock_sock_nested+0xe0/0x130 net/core/sock.c:3500
softirqs last disabled at (820): [<ffff80001043a060>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (820): [<ffff80001043a060>] inet_csk_get_port+0x1d0/0x1404 net/ipv4/inet_connection_sock.c:538
---[ end trace 0000000000000000 ]---


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

syzbot has found a reproducer for the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=155ae658580000

kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=e4f0060517655d9cd5fd
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1355db42580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c37212580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz

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

------------[ cut here ]------------

WARNING: CPU: 0 PID: 4501 at net/ipv4/inet_connection_sock.c:590 inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
Modules linked in:
CPU: 0 PID: 4501 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
lr : inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590

sp : ffff800020db7b30
x29: ffff800020db7c20 x28: ffff0000f21f4000 x27: dfff800000000000
x26: ffff0000d7240120 x25: 0000000000004e20 x24: dfff800000000000
x23: ffff80001c751ee0 x22: ffff0000f21f3080 x21: 1fffe0001acf6e46
x20: ffff0000d67b7230 x19: ffff0000d67b7238 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082d25ac x15: 0000000000000000
x14: 00000000ffff0000 x13: 1ffff00002a180b1 x12: 0000000000ff0100
x11: ff0080001043b098 x10: 0000000000000000 x9 : ffff80001043b098
x8 : ffff0000d209d340 x7 : ffff80000fcd3298 x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000002 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
inet_csk_get_port+0x1208/0x1404 net/ipv4/inet_connection_sock.c:590
inet_csk_listen_start+0x104/0x2c4 net/ipv4/inet_connection_sock.c:1296
inet_dccp_listen+0x194/0x260 net/dccp/proto.c:948
__sys_listen+0x198/0x21c net/socket.c:1845
__do_sys_listen net/socket.c:1854 [inline]
__se_sys_listen net/socket.c:1852 [inline]
__arm64_sys_listen+0x5c/0x74 net/socket.c:1852
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

irq event stamp: 2875
hardirqs last enabled at (2874): [<ffff8000081a8850>] __local_bh_enable_ip+0x1f8/0x380 kernel/softirq.c:426
hardirqs last disabled at (2875): [<ffff80001195cc30>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (2860): [<ffff80000fcd9324>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (2860): [<ffff80000fcd9324>] lock_sock_nested+0xe0/0x130 net/core/sock.c:3500
softirqs last disabled at (2862): [<ffff80001043a060>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (2862): [<ffff80001043a060>] inet_csk_get_port+0x1d0/0x1404 net/ipv4/inet_connection_sock.c:538

---[ end trace 0000000000000000 ]---


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.