netlink: 24 bytes leftover after parsing attributes in process `syz-executor.3'.
================================================================================
UBSAN: Undefined behaviour in arch/x86/kernel/uprobes.c:276:56
index 4 is out of range for type 'insn_byte_t [4]'
CPU: 0 PID: 17818 Comm: syz-executor.2 Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_out_of_bounds.cold+0x63/0x6f lib/ubsan.c:383
 is_prefix_bad arch/x86/kernel/uprobes.c:276 [inline]
 uprobe_init_insn arch/x86/kernel/uprobes.c:299 [inline]
 arch_uprobe_analyze_insn+0x9d8/0xaa0 arch/x86/kernel/uprobes.c:868
 prepare_uprobe kernel/events/uprobes.c:611 [inline]
 install_breakpoint kernel/events/uprobes.c:654 [inline]
 register_for_each_vma+0xbf5/0xe50 kernel/events/uprobes.c:822
 uprobe_apply+0xeb/0x160 kernel/events/uprobes.c:970
 uprobe_perf_open kernel/trace/trace_uprobe.c:1067 [inline]
 trace_uprobe_register+0x4ac/0x6f0 kernel/trace/trace_uprobe.c:1207
 perf_trace_event_open kernel/trace/trace_event_perf.c:181 [inline]
 perf_trace_event_init kernel/trace/trace_event_perf.c:203 [inline]
 perf_trace_event_init+0x175/0xaa0 kernel/trace/trace_event_perf.c:190
 perf_uprobe_init+0x165/0x200 kernel/trace/trace_event_perf.c:330
 perf_uprobe_event_init+0xf8/0x190 kernel/events/core.c:8588
 perf_try_init_event+0x124/0x2e0 kernel/events/core.c:9861
 perf_init_event kernel/events/core.c:9892 [inline]
 perf_event_alloc.part.0+0x1ba9/0x3000 kernel/events/core.c:10166
 perf_event_alloc kernel/events/core.c:10536 [inline]
 __do_sys_perf_event_open kernel/events/core.c:10637 [inline]
 __se_sys_perf_event_open+0x54e/0x27c0 kernel/events/core.c:10526
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45de59
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f4400e15c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 0000000000024cc0 RCX: 000000000045de59
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 000000000118c018 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 000000000118bfd4
R13: 00007ffd45e86dff R14: 00007f4400e169c0 R15: 000000000118bfd4
================================================================================
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.3'.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
attempt to access beyond end of device
loop5: rw=1, want=230, limit=127
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies.  Check SNMP counters.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.