batman_adv: Cannot find parent device ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26 Read of size 8 at addr ffff888058e074a0 by task syz-executor.1/24862 CPU: 1 PID: 24862 Comm: syz-executor.1 Not tainted 4.19.110-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+0x188/0x20d lib/dump_stack.c:118 print_address_description.cold+0x7c/0x212 mm/kasan/report.c:256 kasan_report_error mm/kasan/report.c:354 [inline] kasan_report mm/kasan/report.c:412 [inline] kasan_report.cold+0x88/0x2b9 mm/kasan/report.c:396 __list_add_valid+0x93/0xa0 lib/list_debug.c:26 __list_add include/linux/list.h:60 [inline] list_add_tail include/linux/list.h:93 [inline] cma_listen_on_all drivers/infiniband/core/cma.c:2380 [inline] rdma_listen+0x609/0x880 drivers/infiniband/core/cma.c:3408 ucma_listen+0x14d/0x1c0 drivers/infiniband/core/ucma.c:1100 ucma_write+0x285/0x350 drivers/infiniband/core/ucma.c:1689 __vfs_write+0xf7/0x760 fs/read_write.c:485 vfs_write+0x206/0x550 fs/read_write.c:549 ksys_write+0x12b/0x2a0 fs/read_write.c:599 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45c849 Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f419b9e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f419b9e66d4 RCX: 000000000045c849 RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000006 RBP: 000000000076bfa0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 0000000000000cc1 R14: 00000000004cee7d R15: 000000000076bfac Allocated by task 24498: set_track mm/kasan/kasan.c:460 [inline] kasan_kmalloc mm/kasan/kasan.c:553 [inline] kasan_kmalloc+0xbf/0xe0 mm/kasan/kasan.c:531 kmem_cache_alloc_trace+0x14d/0x7a0 mm/slab.c:3625 kmalloc include/linux/slab.h:515 [inline] kzalloc include/linux/slab.h:709 [inline] perf_event_alloc.part.0+0xb8/0x2f90 kernel/events/core.c:10033 perf_event_alloc kernel/events/core.c:10520 [inline] __do_sys_perf_event_open+0x902/0x2830 kernel/events/core.c:10621 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 18: set_track mm/kasan/kasan.c:460 [inline] __kasan_slab_free+0xf7/0x140 mm/kasan/kasan.c:521 __cache_free mm/slab.c:3503 [inline] kfree+0xce/0x220 mm/slab.c:3822 __rcu_reclaim kernel/rcu/rcu.h:236 [inline] rcu_do_batch kernel/rcu/tree.c:2584 [inline] invoke_rcu_callbacks kernel/rcu/tree.c:2897 [inline] __rcu_process_callbacks kernel/rcu/tree.c:2864 [inline] rcu_process_callbacks+0xb2d/0x17f0 kernel/rcu/tree.c:2881 __do_softirq+0x26c/0x93c kernel/softirq.c:292 The buggy address belongs to the object at ffff888058e072c0 which belongs to the cache kmalloc-2048 of size 2048 The buggy address is located 480 bytes inside of 2048-byte region [ffff888058e072c0, ffff888058e07ac0) The buggy address belongs to the page: page:ffffea0001638180 count:1 mapcount:0 mapping:ffff88812c3dcc40 index:0xffff888058e061c0 compound_mapcount: 0 flags: 0xfffe0000008100(slab|head) raw: 00fffe0000008100 ffffea0001674388 ffffea000163bc08 ffff88812c3dcc40 raw: ffff888058e061c0 ffff888058e061c0 0000000100000002 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888058e07380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888058e07400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff888058e07480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888058e07500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888058e07580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================