Use struct sctp_assoc_value instead RDS: rds_bind could not find a transport for 172.20.5.170, load rds_tcp or rds_rdma? sctp: [Deprecated]: syz-executor0 (pid 7691) Use of int in maxseg socket option. Use struct sctp_assoc_value instead ================================================================== BUG: KASAN: use-after-free in __le32_to_cpup include/uapi/linux/byteorder/little_endian.h:58 [inline] BUG: KASAN: use-after-free in le32_to_cpuvp crypto/chacha20_generic.c:19 [inline] BUG: KASAN: use-after-free in crypto_chacha20_init crypto/chacha20_generic.c:58 [inline] BUG: KASAN: use-after-free in crypto_chacha20_crypt+0xaf1/0xbd0 crypto/chacha20_generic.c:91 Read of size 4 at addr ffff8801cf028900 by task kworker/0:7/20305 CPU: 0 PID: 20305 Comm: kworker/0:7 Not tainted 4.15.0-rc3+ #156 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: crypto cryptd_queue_worker Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x194/0x257 lib/dump_stack.c:53 print_address_description+0x73/0x250 mm/kasan/report.c:252 kasan_report_error mm/kasan/report.c:351 [inline] kasan_report+0x25b/0x340 mm/kasan/report.c:409 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:429 __le32_to_cpup include/uapi/linux/byteorder/little_endian.h:58 [inline] le32_to_cpuvp crypto/chacha20_generic.c:19 [inline] crypto_chacha20_init crypto/chacha20_generic.c:58 [inline] crypto_chacha20_crypt+0xaf1/0xbd0 crypto/chacha20_generic.c:91 chacha20_simd+0xe4/0x410 arch/x86/crypto/chacha20_glue.c:78 crypto_skcipher_decrypt include/crypto/skcipher.h:463 [inline] cryptd_skcipher_decrypt+0x2de/0x5a0 crypto/cryptd.c:523 cryptd_queue_worker+0xff/0x1b0 crypto/cryptd.c:190 process_one_work+0xbf3/0x1bc0 kernel/workqueue.c:2112 worker_thread+0x223/0x1990 kernel/workqueue.c:2246 kthread+0x33c/0x400 kernel/kthread.c:238 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:441 Allocated by task 7612: save_stack+0x43/0xd0 mm/kasan/kasan.c:447 set_track mm/kasan/kasan.c:459 [inline] kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551 kmem_cache_alloc_trace+0x136/0x750 mm/slab.c:3610 kmalloc include/linux/slab.h:499 [inline] kzalloc include/linux/slab.h:688 [inline] xfrm_state_alloc+0xb8/0x630 net/xfrm/xfrm_state.c:565 pfkey_msg2xfrm_state net/key/af_key.c:1109 [inline] pfkey_add+0x71b/0x3270 net/key/af_key.c:1491 pfkey_process+0x60b/0x720 net/key/af_key.c:2809 pfkey_sendmsg+0x4d6/0x9f0 net/key/af_key.c:3648 sock_sendmsg_nosec net/socket.c:636 [inline] sock_sendmsg+0xca/0x110 net/socket.c:646 ___sys_sendmsg+0x755/0x890 net/socket.c:2026 __sys_sendmsg+0xe5/0x210 net/socket.c:2060 SYSC_sendmsg net/socket.c:2071 [inline] SyS_sendmsg+0x2d/0x50 net/socket.c:2067 entry_SYSCALL_64_fastpath+0x1f/0x96 Freed by task 20305: save_stack+0x43/0xd0 mm/kasan/kasan.c:447 set_track mm/kasan/kasan.c:459 [inline] kasan_slab_free+0x71/0xc0 mm/kasan/kasan.c:524 __cache_free mm/slab.c:3488 [inline] kfree+0xca/0x250 mm/slab.c:3803 xfrm_state_gc_destroy net/xfrm/xfrm_state.c:453 [inline] xfrm_state_gc_task+0x53e/0x6c0 net/xfrm/xfrm_state.c:469 process_one_work+0xbf3/0x1bc0 kernel/workqueue.c:2112 worker_thread+0x223/0x1990 kernel/workqueue.c:2246 kthread+0x33c/0x400 kernel/kthread.c:238 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:441 The buggy address belongs to the object at ffff8801cf028900 which belongs to the cache kmalloc-1024 of size 1024 The buggy address is located 0 bytes inside of 1024-byte region [ffff8801cf028900, ffff8801cf028d00) The buggy address belongs to the page: page:000000000936e17c count:1 mapcount:0 mapping:00000000486480ce index:0x0 compound_mapcount: 0 flags: 0x2fffc0000008100(slab|head) raw: 02fffc0000008100 ffff8801cf028000 0000000000000000 0000000100000007 raw: ffffea0007371720 ffffea000674ed20 ffff8801db000ac0 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8801cf028800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8801cf028880: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff8801cf028900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8801cf028980: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8801cf028a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================