Bearer rejected, not supported in standalone mode ================================================================== BUG: KASAN: slab-out-of-bounds in primary_event_id kernel/events/core.c:1316 [inline] BUG: KASAN: slab-out-of-bounds in perf_output_read_group kernel/events/core.c:5897 [inline] BUG: KASAN: slab-out-of-bounds in perf_output_read+0x1046/0x1090 kernel/events/core.c:5932 Read of size 8 at addr ffff888095fdafe0 by task syz-executor.4/10586 CPU: 0 PID: 10586 Comm: syz-executor.4 Not tainted 4.14.299-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252 kasan_report_error.cold+0x8a/0x191 mm/kasan/report.c:351 kasan_report mm/kasan/report.c:409 [inline] __asan_report_load8_noabort+0x68/0x70 mm/kasan/report.c:430 primary_event_id kernel/events/core.c:1316 [inline] perf_output_read_group kernel/events/core.c:5897 [inline] perf_output_read+0x1046/0x1090 kernel/events/core.c:5932 perf_output_sample+0xa28/0x16f0 kernel/events/core.c:5974 __perf_event_output kernel/events/core.c:6287 [inline] perf_event_output_forward+0xf8/0x1f0 kernel/events/core.c:6300 __perf_event_overflow+0x113/0x310 kernel/events/core.c:7549 perf_swevent_overflow kernel/events/core.c:7625 [inline] perf_swevent_event+0x299/0x460 kernel/events/core.c:7653 do_perf_sw_event kernel/events/core.c:7766 [inline] ___perf_sw_event+0x2a1/0x480 kernel/events/core.c:7797 __perf_sw_event+0x4f/0x100 kernel/events/core.c:7809 perf_sw_event include/linux/perf_event.h:1046 [inline] __do_page_fault+0x692/0xad0 arch/x86/mm/fault.c:1483 page_fault+0x25/0x50 arch/x86/entry/entry_64.S:1126 Allocated by task 7995: save_stack mm/kasan/kasan.c:447 [inline] set_track mm/kasan/kasan.c:459 [inline] kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551 __do_kmalloc_node mm/slab.c:3682 [inline] __kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3696 __kmalloc_reserve net/core/skbuff.c:137 [inline] __alloc_skb+0x96/0x510 net/core/skbuff.c:205 alloc_skb include/linux/skbuff.h:980 [inline] bt_skb_alloc include/net/bluetooth/bluetooth.h:336 [inline] hci_prepare_cmd+0x2a/0x290 net/bluetooth/hci_request.c:302 hci_send_cmd+0x3c/0x140 net/bluetooth/hci_core.c:3431 hci_conn_request_evt net/bluetooth/hci_event.c:2312 [inline] hci_event_packet+0x4686/0x7510 net/bluetooth/hci_event.c:5325 hci_rx_work+0x427/0xb40 net/bluetooth/hci_core.c:4266 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406 Freed by task 0: (stack is not available) The buggy address belongs to the object at ffff888095fdad00 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 224 bytes to the right of 512-byte region [ffff888095fdad00, ffff888095fdaf00) The buggy address belongs to the page: page:ffffea000257f680 count:1 mapcount:0 mapping:ffff888095fda080 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffff888095fda080 0000000000000000 0000000100000006 raw: ffffea000278e5e0 ffffea00023ebbe0 ffff88813fe74940 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888095fdae80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888095fdaf00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff888095fdaf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff888095fdb000: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb ffff888095fdb080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================