KASAN: slab-out-of-bounds Write in tcf_queue_work

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 14cfdbd3 Linux 4.19.112
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17011be3e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=48ea0e0a21a4900f
dashboard link: https://syzkaller.appspot.com/bug?extid=ce592d1424bb95d8d938
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ce592d...@syzkaller.appspotmail.com

device veth1_macvtap left promiscuous mode
device veth0_macvtap left promiscuous mode
device veth1_vlan left promiscuous mode
device veth0_vlan left promiscuous mode
==================================================================
BUG: KASAN: slab-out-of-bounds in __lockdep_init_map+0x529/0x5a0 kernel/locking/lockdep.c:3179
Write of size 8 at addr ffff888098f2fb90 by task kworker/u4:7/20604

CPU: 0 PID: 20604 Comm: kworker/u4:7 Not tainted 4.19.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
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
__lockdep_init_map+0x529/0x5a0 kernel/locking/lockdep.c:3179
tcf_queue_work+0x5b/0xf0 net/sched/cls_api.c:137
route4_queue_work net/sched/cls_route.c:276 [inline]
route4_destroy+0x4a9/0x7e0 net/sched/cls_route.c:302
tcf_proto_destroy+0x5d/0xe0 net/sched/cls_api.c:190
tcf_chain_flush+0x1ed/0x330 net/sched/cls_api.c:362
tcf_block_put_ext.part.0+0x418/0x9a0 net/sched/cls_api.c:770
tcf_block_put_ext net/sched/cls_api.c:754 [inline]
tcf_block_put+0xad/0xf8 net/sched/cls_api.c:797
hfsc_destroy_qdisc+0xe0/0x280 net/sched/sch_hfsc.c:1509
qdisc_destroy+0x17c/0x6b0 net/sched/sch_generic.c:982
dev_shutdown+0x2b5/0x47a net/sched/sch_generic.c:1300
rollback_registered_many+0x64a/0xc40 net/core/dev.c:8173
unregister_netdevice_many.part.0+0x16/0x1e0 net/core/dev.c:9294
unregister_netdevice_many net/core/dev.c:9293 [inline]
default_device_exit_batch+0x2ff/0x3c0 net/core/dev.c:9765
ops_exit_list.isra.0+0xef/0x140 net/core/net_namespace.c:156
cleanup_net+0x3bf/0x850 net/core/net_namespace.c:553
process_one_work+0x91f/0x1640 kernel/workqueue.c:2155
worker_thread+0x96/0xe20 kernel/workqueue.c:2298
kthread+0x34a/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Allocated by task 30470:
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
__do_kmalloc mm/slab.c:3727 [inline]
__kmalloc+0x15b/0x770 mm/slab.c:3736
kmalloc include/linux/slab.h:520 [inline]
kzalloc include/linux/slab.h:709 [inline]
crypto_create_tfm+0x79/0x2f0 crypto/api.c:463
crypto_spawn_tfm2+0x5c/0xb0 crypto/algapi.c:709
crypto_spawn_ahash include/crypto/internal/hash.h:189 [inline]
crypto_authenc_init_tfm+0x3f/0x290 crypto/authenc.c:332
crypto_aead_init_tfm+0x138/0x1a0 crypto/aead.c:113
crypto_create_tfm+0xd5/0x2f0 crypto/api.c:470
crypto_alloc_tfm+0xff/0x2d0 crypto/api.c:542
esp_init_authenc+0x1d5/0x8c0 net/ipv6/esp6.c:818
esp6_init_state+0x309/0x3a0 net/ipv6/esp6.c:890
__xfrm_init_state+0x55c/0xf20 net/xfrm/xfrm_state.c:2314
xfrm_state_construct net/xfrm/xfrm_user.c:625 [inline]
xfrm_add_sa+0x1f8a/0x3527 net/xfrm/xfrm_user.c:682
xfrm_user_rcv_msg+0x40c/0x6b0 net/xfrm/xfrm_user.c:2677
netlink_rcv_skb+0x160/0x410 net/netlink/af_netlink.c:2455
xfrm_netlink_rcv+0x6b/0x90 net/xfrm/xfrm_user.c:2685
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d7/0x6a0 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x80b/0xcd0 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:632
sock_no_sendpage+0xf8/0x140 net/core/sock.c:2645
kernel_sendpage+0x82/0xd0 net/socket.c:3378
sock_sendpage+0x84/0xa0 net/socket.c:847
pipe_to_sendpage+0x263/0x320 fs/splice.c:452
splice_from_pipe_feed fs/splice.c:503 [inline]
__splice_from_pipe+0x38f/0x7a0 fs/splice.c:627
splice_from_pipe+0xd9/0x140 fs/splice.c:662
do_splice_from fs/splice.c:852 [inline]
do_splice+0x5ea/0x1250 fs/splice.c:1154
__do_sys_splice fs/splice.c:1428 [inline]
__se_sys_splice fs/splice.c:1408 [inline]
__x64_sys_splice+0x2b5/0x320 fs/splice.c:1408
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 23:
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
route4_delete_filter_work+0x17/0x20 net/sched/cls_route.c:270
process_one_work+0x91f/0x1640 kernel/workqueue.c:2155
worker_thread+0x96/0xe20 kernel/workqueue.c:2298
kthread+0x34a/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

The buggy address belongs to the object at ffff888098f2fb00
which belongs to the cache kmalloc-192 of size 192
The buggy address is located 144 bytes inside of
192-byte region [ffff888098f2fb00, ffff888098f2fbc0)
The buggy address belongs to the page:
page:ffffea000263cbc0 count:1 mapcount:0 mapping:ffff88812c3dc040 index:0x0
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea0002955548 ffffea00023c2008 ffff88812c3dc040
raw: 0000000000000000 ffff888098f2f000 0000000100000010 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff888098f2fa80: 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888098f2fb00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888098f2fb80: 00 00 fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff888098f2fc00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888098f2fc80: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc
==================================================================


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.