==================================================================
BUG: KASAN: out-of-bounds in check_canary_byte mm/kfence/core.c:211 [inline]
BUG: KASAN: out-of-bounds in for_each_canary mm/kfence/core.c:245 [inline]
BUG: KASAN: out-of-bounds in kfence_guarded_free+0x7f1/0x8f0 mm/kfence/core.c:374
Read of size 1 at addr ffff88823bd34c51 by task syz-executor.0/32459

CPU: 1 PID: 32459 Comm: syz-executor.0 Not tainted 5.10.0-next-20201223-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x107/0x163 lib/dump_stack.c:120
 print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:230
 __kasan_report mm/kasan/report.c:396 [inline]
 kasan_report.cold+0x79/0xd5 mm/kasan/report.c:413
 check_canary_byte mm/kfence/core.c:211 [inline]
 for_each_canary mm/kfence/core.c:245 [inline]
 kfence_guarded_free+0x7f1/0x8f0 mm/kfence/core.c:374
 __kfence_free+0x70/0x150 mm/kfence/core.c:756
 do_slab_free mm/slub.c:3145 [inline]
 slab_free mm/slub.c:3158 [inline]
 kfree+0x57c/0x5c0 mm/slub.c:4156
 skb_free_head net/core/skbuff.c:595 [inline]
 skb_release_data+0x6d9/0x910 net/core/skbuff.c:615
 skb_release_all net/core/skbuff.c:669 [inline]
 __kfree_skb net/core/skbuff.c:683 [inline]
 kfree_skb net/core/skbuff.c:701 [inline]
 kfree_skb+0x133/0x3f0 net/core/skbuff.c:695
 skb_queue_purge+0x14/0x30 net/core/skbuff.c:3086
 packet_release+0x75f/0xc90 net/packet/af_packet.c:3102
 __sock_release+0xcd/0x280 net/socket.c:597
 sock_close+0x18/0x20 net/socket.c:1256
 __fput+0x283/0x920 fs/file_table.c:280
 task_work_run+0xdd/0x190 kernel/task_work.c:140
 exit_task_work include/linux/task_work.h:30 [inline]
 do_exit+0xb89/0x29e0 kernel/exit.c:823
 do_group_exit+0x125/0x310 kernel/exit.c:920
 get_signal+0x3ec/0x2010 kernel/signal.c:2770
 arch_do_signal_or_restart+0x2a8/0x1eb0 arch/x86/kernel/signal.c:811
 handle_signal_work kernel/entry/common.c:147 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:171 [inline]
 exit_to_user_mode_prepare+0x148/0x250 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
 syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:302
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e299
Code: Unable to access opcode bytes at RIP 0x45e26f.
RSP: 002b:00007f7e64bebc68 EFLAGS: 00000246 ORIG_RAX: 000000000000010e
RAX: fffffffffffffdfe RBX: 0000000000000006 RCX: 000000000045e299
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000040
RBP: 000000000119bfd8 R08: 0000000020000200 R09: 0000000000000000
R10: 0000000020000140 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffe165cd2cf R14: 00007f7e64bec9c0 R15: 000000000119bf8c

Allocated by task 0:
(stack is not available)

The buggy address belongs to the object at ffff88823bd34000
 which belongs to the cache kmalloc-2k of size 2048
The buggy address is located 1105 bytes to the right of
 2048-byte region [ffff88823bd34000, ffff88823bd34800)
The buggy address belongs to the page:
page:00000000e9493340 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x23bd34
flags: 0x57ff00000001200(slab|reserved)
raw: 057ff00000001200 ffffea0008ef4d08 ffffea0008ef4d08 ffff888010042000
raw: 0000000000000000 0000000000010000 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88823bd34b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88823bd34b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88823bd34c00: 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00
                                                 ^
 ffff88823bd34c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88823bd34d00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================