TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. ================================================================== BUG: KASAN: use-after-free in list_replace include/linux/list.h:141 [inline] BUG: KASAN: use-after-free in list_replace_init include/linux/list.h:149 [inline] BUG: KASAN: use-after-free in padata_parallel_worker+0x2b0/0x2e0 kernel/padata.c:76 Write of size 8 at addr ffff8880a1198098 by task kworker/0:3/8761 CPU: 0 PID: 8761 Comm: kworker/0:3 Not tainted 4.14.222-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: pencrypt padata_parallel_worker 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_store8_noabort+0x68/0x70 mm/kasan/report.c:435 list_replace include/linux/list.h:141 [inline] list_replace_init include/linux/list.h:149 [inline] padata_parallel_worker+0x2b0/0x2e0 kernel/padata.c:76 process_one_work+0x793/0x14a0 kernel/workqueue.c:2116 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404 Allocated by task 25542: 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 mm/slab.c:3720 [inline] __kmalloc+0x15a/0x400 mm/slab.c:3729 kmalloc include/linux/slab.h:493 [inline] kzalloc include/linux/slab.h:661 [inline] tls_push_record+0xfa/0x1270 net/tls/tls_sw.c:250 tls_sw_sendmsg+0xbb0/0xfd0 net/tls/tls_sw.c:457 inet_sendmsg+0x11a/0x4e0 net/ipv4/af_inet.c:762 sock_sendmsg_nosec net/socket.c:646 [inline] sock_sendmsg+0xb5/0x100 net/socket.c:656 SYSC_sendto net/socket.c:1763 [inline] SyS_sendto+0x1c7/0x2c0 net/socket.c:1731 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb Freed by task 25542: save_stack mm/kasan/kasan.c:447 [inline] set_track mm/kasan/kasan.c:459 [inline] kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524 __cache_free mm/slab.c:3496 [inline] kfree+0xc9/0x250 mm/slab.c:3815 tls_push_record+0xc3b/0x1270 net/tls/tls_sw.c:293 tls_sw_sendmsg+0xbb0/0xfd0 net/tls/tls_sw.c:457 inet_sendmsg+0x11a/0x4e0 net/ipv4/af_inet.c:762 sock_sendmsg_nosec net/socket.c:646 [inline] sock_sendmsg+0xb5/0x100 net/socket.c:656 SYSC_sendto net/socket.c:1763 [inline] SyS_sendto+0x1c7/0x2c0 net/socket.c:1731 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb The buggy address belongs to the object at ffff8880a1198040 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 88 bytes inside of 256-byte region [ffff8880a1198040, ffff8880a1198140) The buggy address belongs to the page: page:ffffea0002846600 count:1 mapcount:0 mapping:ffff8880a1198040 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffff8880a1198040 0000000000000000 000000010000000c raw: ffffea00025ad960 ffffea0002548ba0 ffff88813fe807c0 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880a1197f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8880a1198000: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb >ffff8880a1198080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880a1198100: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ffff8880a1198180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================