Hello, syzbot found the following issue on: HEAD commit: d887ae3247e0 octeontx2-pf: Remove unnecessary synchronize_.. git tree: net-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=118621f1f00000 kernel config: https://syzkaller.appspot.com/x/.config?x=b1aab282dc5dd920 dashboard link: https://syzkaller.appspot.com/bug?extid=4903218f7fba0a2d6226 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c775bef00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1428ee59f00000 The issue was bisected to: commit 2794cdb0b97bfe62d25c996c8afe4832207e78bc Author: Florian Westphal <fw@xxxxxxxxx> Date: Mon Apr 25 13:15:41 2022 +0000 netfilter: nfnetlink: allow to detect if ctnetlink listeners exist bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14885b35f00000 final oops: https://syzkaller.appspot.com/x/report.txt?x=16885b35f00000 console output: https://syzkaller.appspot.com/x/log.txt?x=12885b35f00000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+4903218f7fba0a2d6226@xxxxxxxxxxxxxxxxxxxxxxxxx Fixes: 2794cdb0b97b ("netfilter: nfnetlink: allow to detect if ctnetlink listeners exist") ================================================================================ UBSAN: array-index-out-of-bounds in net/netfilter/nfnetlink.c:697:28 index 10 is out of range for type 'int [10]' CPU: 1 PID: 3606 Comm: syz-executor222 Not tainted 5.18.0-rc6-syzkaller-01525-gd887ae3247e0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 ubsan_epilogue+0xb/0x50 lib/ubsan.c:151 __ubsan_handle_out_of_bounds.cold+0x62/0x6c lib/ubsan.c:283 nfnetlink_unbind+0x38c/0x3b0 net/netfilter/nfnetlink.c:697 netlink_release+0xa8f/0x1db0 net/netlink/af_netlink.c:773 __sock_release+0xcd/0x280 net/socket.c:650 sock_close+0x18/0x20 net/socket.c:1365 __fput+0x277/0x9d0 fs/file_table.c:317 task_work_run+0xdd/0x1a0 kernel/task_work.c:164 exit_task_work include/linux/task_work.h:37 [inline] do_exit+0xaff/0x2a00 kernel/exit.c:795 do_group_exit+0xd2/0x2f0 kernel/exit.c:925 __do_sys_exit_group kernel/exit.c:936 [inline] __se_sys_exit_group kernel/exit.c:934 [inline] __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:934 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f23ae868639 Code: Unable to access opcode bytes at RIP 0x7f23ae86860f. RSP: 002b:00007ffe9dd00178 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f23ae8dc270 RCX: 00007f23ae868639 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f23ae8dc270 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001 </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@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
