==================================================================
BUG: KASAN: slab-out-of-bounds in predicate_parse kernel/trace/trace_events_filter.c:557 [inline]
BUG: KASAN: slab-out-of-bounds in process_preds+0x1958/0x19b0 kernel/trace/trace_events_filter.c:1505
Write of size 4 at addr ffff8801dad75370 by task syzkaller210155/4453

CPU: 1 PID: 4453 Comm: syzkaller210155 Not tainted 4.16.0+ #17
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+0x1b9/0x294 lib/dump_stack.c:113
 print_address_description+0x6c/0x20b mm/kasan/report.c:256
 kasan_report_error mm/kasan/report.c:354 [inline]
 kasan_report.cold.7+0xac/0x2f5 mm/kasan/report.c:412
 __asan_report_store4_noabort+0x17/0x20 mm/kasan/report.c:437
 predicate_parse kernel/trace/trace_events_filter.c:557 [inline]
 process_preds+0x1958/0x19b0 kernel/trace/trace_events_filter.c:1505
 create_filter+0x1a8/0x370 kernel/trace/trace_events_filter.c:1714
 ftrace_profile_set_filter+0x109/0x2b0 kernel/trace/trace_events_filter.c:2042
 perf_event_set_filter+0x248/0x1230 kernel/events/core.c:9064
 _perf_ioctl+0x84c/0x1650 kernel/events/core.c:5056
 perf_ioctl+0x59/0x80 kernel/events/core.c:5107
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:500 [inline]
 do_vfs_ioctl+0x1cf/0x1650 fs/ioctl.c:684
 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701
 SYSC_ioctl fs/ioctl.c:708 [inline]
 SyS_ioctl+0x24/0x30 fs/ioctl.c:706
 do_syscall_64+0x29e/0x9d0 arch/x86/entry/common.c:287
 entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x43fde9
RSP: 002b:00007ffdc01b5fd8 EFLAGS: 00000213 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043fde9
RDX: 00000000200000c0 RSI: 0000000040082406 RDI: 0000000000000003
RBP: 00000000006ca018 R08: 00000000004002c8 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000213 R12: 0000000000401710
R13: 00000000004017a0 R14: 0000000000000000 R15: 0000000000000000

Allocated by task 0:
 save_stack+0x43/0xd0 mm/kasan/kasan.c:448
 set_track mm/kasan/kasan.c:460 [inline]
 kasan_kmalloc+0xc4/0xe0 mm/kasan/kasan.c:553
 kmem_cache_alloc_trace+0x152/0x780 mm/slab.c:3620
 kmalloc include/linux/slab.h:512 [inline]
 kzalloc include/linux/slab.h:701 [inline]
 allocate_cgrp_cset_links+0x257/0x350 kernel/cgroup/cgroup.c:1052
 cgroup_setup_root+0x2a7/0xd70 kernel/cgroup/cgroup.c:1902
 cgroup_init+0x2db/0xc63 kernel/cgroup/cgroup.c:5267
 start_kernel+0x897/0x923 init/main.c:719
 x86_64_start_reservations+0x29/0x2b arch/x86/kernel/head64.c:443
 x86_64_start_kernel+0x76/0x79 arch/x86/kernel/head64.c:424
 secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:242

Freed by task 0:
(stack is not available)

The buggy address belongs to the object at ffff8801dad75300
 which belongs to the cache kmalloc-64 of size 64
The buggy address is located 48 bytes to the right of
 64-byte region [ffff8801dad75300, ffff8801dad75340)
The buggy address belongs to the page:
page:ffffea00076b5d40 count:1 mapcount:0 mapping:ffff8801dad75000 index:0x0
flags: 0x2fffc0000000100(slab)
raw: 02fffc0000000100 ffff8801dad75000 0000000000000000 0000000100000020
raw: ffffea00076b0560 ffff8801dac01348 ffff8801dac00340 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8801dad75200: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
 ffff8801dad75280: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc
>ffff8801dad75300: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc
                                                             ^
 ffff8801dad75380: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc
 ffff8801dad75400: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc
==================================================================