general protection fault in perf_tp_event_match

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17471909900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=243f17adc878b3392acd
compiler: gcc (GCC) 10.1.0-syz 20200507

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

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

netlink: 8 bytes leftover after parsing attributes in process `syz-executor.5'.
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 6375 Comm: syz-executor.0 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880576f0380 task.stack: ffff8880576f8000
RIP: 0010:perf_tp_event_match.constprop.0+0x29/0x1d0 kernel/events/core.c:8021
RSP: 0018:ffff8880576ff918 EFLAGS: 00010003
RAX: dffffc0000000000 RBX: 000018e70301008f RCX: 000000000000002c
RDX: 0000031ce0602049 RSI: ffff8880576ffa00 RDI: 000018e70301024f
RBP: ffff8880576ffa00 R08: ffff8880aea27ac0 R09: ffff8880aea00000
R10: ffff8880576ffc38 R11: ffff8880576f0380 R12: ffff8880aea00000
R13: ffff8880576ffa00 R14: dffffc0000000000 R15: ffff88809152c3c0
FS: 0000000001827940(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a5374 CR3: 0000000057605000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
perf_tp_event+0x51e/0x6e0 kernel/events/core.c:8078
perf_trace_run_bpf_submit+0x119/0x200 kernel/events/core.c:8049
perf_trace_sched_wakeup_template+0x331/0x470 include/trace/events/sched.h:57
trace_sched_wakeup_new include/trace/events/sched.h:103 [inline]
wake_up_new_task+0x658/0xa70 kernel/sched/core.c:2480
_do_fork+0x221/0xc80 kernel/fork.c:2095
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45c74a
RSP: 002b:00007ffc82dcd030 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffc82dcd030 RCX: 000000000045c74a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007ffc82dcd070 R08: 0000000000000001 R09: 0000000001827940
R10: 0000000001827c10 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007ffc82dcd0c0
Code: 00 00 41 55 41 54 55 48 89 f5 53 48 89 fb e8 0f b5 f1 ff 48 8d bb c0 01 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 51 01 00 00 f6 83 c0 01 00
RIP: perf_tp_event_match.constprop.0+0x29/0x1d0 kernel/events/core.c:8021 RSP: ffff8880576ff918

======================================================


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.