[Android 5.15] BUG: soft lockup in sys_socket

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=10dcb833180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=cf71edbddb0657f4f402
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb03d3180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13037f9d180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4098d24d4c8b/disk-993bed18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/94fbc07ac02d/vmlinux-993bed18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eed14de06c19/bzImage-993bed18.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 246s! [init:617]
Modules linked in:
CPU: 0 PID: 617 Comm: init Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
RIP: 0010:arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
RIP: 0010:kvm_wait+0x147/0x180 arch/x86/kernel/kvm.c:918
Code: 4c 89 e8 48 c1 e8 03 42 0f b6 04 20 84 c0 44 8b 74 24 1c 75 34 41 0f b6 45 00 44 38 f0 75 10 66 90 0f 00 2d 5b 03 f3 03 fb f4 <e9> 24 ff ff ff fb e9 1e ff ff ff 44 89 e9 80 e1 07 38 c1 7c a3 4c
RSP: 0018:ffffc900007d7500 EFLAGS: 00000246
RAX: 0000000000000001 RBX: 1ffff920000faea4 RCX: 1ffffffff0d1aa9c
RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff8881f7037ed4
RBP: ffffc900007d75b0 R08: dffffc0000000000 R09: ffffed103ee06fdb
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8881f7037ed4 R14: 0000000000000001 R15: 1ffff920000faea8
FS: 00007f626f60c380(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ba1a370dc0 CR3: 000000010b909000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
pv_wait arch/x86/include/asm/paravirt.h:597 [inline]
pv_wait_node kernel/locking/qspinlock_paravirt.h:325 [inline]
__pv_queued_spin_lock_slowpath+0x41b/0xc40 kernel/locking/qspinlock.c:473
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:585 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
do_raw_spin_lock include/linux/spinlock.h:187 [inline]
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x139/0x1b0 kernel/locking/spinlock.c:178
sock_hash_delete_elem+0xb1/0x2f0 net/core/sock_map.c:937
bpf_prog_3ffd2c70e20892c6+0x3a/0x584
bpf_dispatcher_nop_func include/linux/bpf.h:785 [inline]
__bpf_prog_run include/linux/filter.h:625 [inline]
bpf_prog_run include/linux/filter.h:632 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1883 [inline]
bpf_trace_run2+0xec/0x210 kernel/trace/bpf_trace.c:1920
__bpf_trace_kfree+0x6f/0x90 include/trace/events/kmem.h:118
trace_kfree include/trace/events/kmem.h:118 [inline]
kfree+0x1f3/0x220 mm/slub.c:4569
context_destroy security/selinux/ss/context.h:177 [inline]
security_compute_sid+0x1d7d/0x1f40 security/selinux/ss/services.c:1913
security_transition_sid+0x7d/0x90 security/selinux/ss/services.c:1936
socket_sockcreate_sid security/selinux/hooks.c:4650 [inline]
selinux_socket_create+0x204/0x330 security/selinux/hooks.c:4684
security_socket_create+0x77/0xb0 security/security.c:2185
__sock_create+0xd6/0x760 net/socket.c:1441
sock_create net/socket.c:1537 [inline]
__sys_socket+0x132/0x370 net/socket.c:1579
__do_sys_socket net/socket.c:1588 [inline]
__se_sys_socket net/socket.c:1586 [inline]
__x64_sys_socket+0x7a/0x90 net/socket.c:1586
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f626f76ebd7
Code: 73 01 c3 48 8b 0d 51 c2 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 29 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 21 c2 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffd6364a818 EFLAGS: 00000202
ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f626f76ebd7
RDX: 0000000000000000 RSI: 0000000000080002 RDI: 0000000000000001
RBP: 0000000000000002 R08: 0000000000000000 R09: 2589363724c28f9a
R10: 0000000000000008 R11: 0000000000000202 R12: 00007f626f7fabc0
R13: 00007f626f8fc212 R14: 00007ffd6364a948 R15: 0000000000000000
</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 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.

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