================================================================== BUG: KASAN: double-free in kfree_skbmem+0x15c/0x1ec Free of addr ffff0000edc02b40 by task kworker/u9:2/6277 CPU: 1 PID: 6277 Comm: kworker/u9:2 Tainted: G W 6.10.0-rc2-syzkaller-g8867bbd4a056 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Workqueue: hci3 hci_rx_work Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:317 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:324 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x198/0x538 mm/kasan/report.c:488 kasan_report_invalid_free+0xc4/0x118 mm/kasan/report.c:563 poison_slab_object+0x140/0x180 mm/kasan/common.c:232 __kasan_slab_free+0x3c/0x70 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2195 [inline] slab_free mm/slub.c:4436 [inline] kmem_cache_free+0x178/0x4e4 mm/slub.c:4511 kfree_skbmem+0x15c/0x1ec __kfree_skb net/core/skbuff.c:1188 [inline] kfree_skb_reason+0x1c8/0x4a4 net/core/skbuff.c:1223 kfree_skb include/linux/skbuff.h:1257 [inline] hci_req_sync_complete+0xb0/0x248 net/bluetooth/hci_request.c:109 hci_event_packet+0xab8/0x105c net/bluetooth/hci_event.c:7479 hci_rx_work+0x318/0xa78 net/bluetooth/hci_core.c:4074 process_one_work+0x7b0/0x15e8 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x938/0xef4 kernel/workqueue.c:3393 kthread+0x288/0x310 kernel/kthread.c:389 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 Allocated by task 6282: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x40/0x50 mm/kasan/generic.c:565 unpoison_slab_object mm/kasan/common.c:312 [inline] __kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:338 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3940 [inline] slab_alloc_node mm/slub.c:4000 [inline] kmem_cache_alloc_noprof+0x1c0/0x350 mm/slub.c:4007 skb_clone+0x1c8/0x330 net/core/skbuff.c:2052 hci_send_cmd_sync net/bluetooth/hci_core.c:4123 [inline] hci_cmd_work+0x174/0x568 net/bluetooth/hci_core.c:4143 process_one_work+0x7b0/0x15e8 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x938/0xef4 kernel/workqueue.c:3393 kthread+0x288/0x310 kernel/kthread.c:389 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860 The buggy address belongs to the object at ffff0000edc02b40 which belongs to the cache skbuff_head_cache of size 240 The buggy address is located 0 bytes inside of 240-byte region [ffff0000edc02b40, ffff0000edc02c30) The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x12dc02 flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff) page_type: 0xffffefff(slab) raw: 05ffc00000000000 ffff0000c1bcc780 dead000000000122 0000000000000000 raw: 0000000000000000 00000000000c000c 00000001ffffefff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff0000edc02a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0000edc02a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc >ffff0000edc02b00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb ^ ffff0000edc02b80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff0000edc02c00: fb fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc ==================================================================