[v6.1] general protection fault in inet_unhash

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11dd7915280000
kernel config: https://syzkaller.appspot.com/x/.config?x=623aacf949348d7d
dashboard link: https://syzkaller.appspot.com/bug?extid=b8f203173a7bcfa2b70b
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ed651ed0d8f/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8d3199c542c/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a44812549bf7/bzImage-d2869ace.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:inet_ehash_lockp include/net/inet_hashtables.h:209 [inline]
RIP: 0010:inet_unhash+0x1ec/0x870 net/ipv4/inet_hashtables.c:793
Code: 5f 5d c3 49 8d 6c 24 08 48 89 e8 48 c1 e8 03 42 0f b6 04 30 84 c0 0f 85 38 05 00 00 8b 6d 00 48 8d 7b 08 48 89 f8 48 c1 e8 03 <42> 80 3c 30 00 74 05 e8 58 79 d8 f8 48 8b 7b 08 48 83 c3 14 48 89
RSP: 0018:ffffc900001b77b8 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffff8880126b9dc0
RDX: ffff8880126b9dc0 RSI: 0000000000000004 RDI: 0000000000000008
RBP: 0000000012174fb1 R08: ffffffff8907a254 R09: ffffffff8909770d
R10: 0000000000000002 R11: ffff8880126b9dc0 R12: ffff88807699b000
R13: ffff88807699b028 R14: dffffc0000000000 R15: ffff88807699b070
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020250000 CR3: 000000007d627000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
tcp_set_state+0x3d9/0x770 net/ipv4/tcp.c:2748
tcp_done+0x103/0x320 net/ipv4/tcp.c:4645
tcp_out_of_resources+0x1f2/0x390 net/ipv4/tcp_timer.c:132
tcp_probe_timer net/ipv4/tcp_timer.c:385 [inline]
tcp_write_timer_handler+0x58a/0x930 net/ipv4/tcp_timer.c:624
tcp_write_timer+0x12e/0x280 net/ipv4/tcp_timer.c:637
call_timer_fn+0x19e/0x6b0 kernel/time/timer.c:1474
expire_timers kernel/time/timer.c:1519 [inline]
__run_timers+0x67c/0x890 kernel/time/timer.c:1790
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1803
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x51b/0xa10 kernel/smpboot.c:164
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:inet_ehash_lockp include/net/inet_hashtables.h:209 [inline]
RIP: 0010:inet_unhash+0x1ec/0x870 net/ipv4/inet_hashtables.c:793
Code: 5f 5d c3 49 8d 6c 24 08 48 89 e8 48 c1 e8 03 42 0f b6 04 30 84 c0 0f 85 38 05 00 00 8b 6d 00 48 8d 7b 08 48 89 f8 48 c1 e8 03 <42> 80 3c 30 00 74 05 e8 58 79 d8 f8 48 8b 7b 08 48 83 c3 14 48 89
RSP: 0018:ffffc900001b77b8 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffff8880126b9dc0
RDX: ffff8880126b9dc0 RSI: 0000000000000004 RDI: 0000000000000008
RBP: 0000000012174fb1 R08: ffffffff8907a254 R09: ffffffff8909770d
R10: 0000000000000002 R11: ffff8880126b9dc0 R12: ffff88807699b000
R13: ffff88807699b028 R14: dffffc0000000000 R15: ffff88807699b070
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020250000 CR3: 000000007d627000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 5f pop %rdi
1: 5d pop %rbp
2: c3 retq
3: 49 8d 6c 24 08 lea 0x8(%r12),%rbp
8: 48 89 e8 mov %rbp,%rax
b: 48 c1 e8 03 shr $0x3,%rax
f: 42 0f b6 04 30 movzbl (%rax,%r14,1),%eax
14: 84 c0 test %al,%al
16: 0f 85 38 05 00 00 jne 0x554
1c: 8b 6d 00 mov 0x0(%rbp),%ebp
1f: 48 8d 7b 08 lea 0x8(%rbx),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
2f: 74 05 je 0x36
31: e8 58 79 d8 f8 callq 0xf8d8798e
36: 48 8b 7b 08 mov 0x8(%rbx),%rdi
3a: 48 83 c3 14 add $0x14,%rbx
3e: 48 rex.W
3f: 89 .byte 0x89


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.