BUG: KASAN: stack-out-of-bounds in xfrm_state_find+0x303d/0x3170 net/xfrm/xfrm_state.c:1042 Read of size 4 at addr ffff8801d141e5e8 by task syzkaller899728/2950 CPU: 0 PID: 2950 Comm: syzkaller899728 Not tainted 4.13.0-rc4+ #30 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:16 [inline] dump_stack+0x194/0x257 lib/dump_stack.c:52 print_address_description+0x7f/0x260 mm/kasan/report.c:252 kasan_report_error mm/kasan/report.c:351 [inline] kasan_report+0x24e/0x340 mm/kasan/report.c:409 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:429 xfrm_state_find+0x303d/0x3170 net/xfrm/xfrm_state.c:1042 xfrm_tmpl_resolve_one net/xfrm/xfrm_policy.c:1470 [inline] xfrm_tmpl_resolve+0x309/0xbf0 net/xfrm/xfrm_policy.c:1514 xfrm_resolve_and_create_bundle+0x102/0x2080 net/xfrm/xfrm_policy.c:1855 xfrm_lookup+0xd39/0x11c0 net/xfrm/xfrm_policy.c:2216 xfrm_lookup_route+0x39/0x1a0 net/xfrm/xfrm_policy.c:2337 ip_route_output_flow+0x7c/0xa0 net/ipv4/route.c:2543 inet_csk_route_req+0x5d8/0x990 net/ipv4/inet_connection_sock.c:550 tcp_v4_send_synack+0x1e4/0x270 net/ipv4/tcp_ipv4.c:871 tcp_rtx_synack+0x119/0x2e0 net/ipv4/tcp_output.c:3713 inet_rtx_syn_ack+0x64/0xd0 net/ipv4/inet_connection_sock.c:634 tcp_check_req+0xae3/0x1620 net/ipv4/tcp_minisocks.c:615 tcp_v4_rcv+0x168e/0x2df0 net/ipv4/tcp_ipv4.c:1725 ip_local_deliver_finish+0x2e2/0xba0 net/ipv4/ip_input.c:216 NF_HOOK include/linux/netfilter.h:248 [inline] ip_local_deliver+0x1ce/0x6d0 net/ipv4/ip_input.c:257 dst_input include/net/dst.h:477 [inline] ip_rcv_finish+0x8db/0x19c0 net/ipv4/ip_input.c:397 NF_HOOK include/linux/netfilter.h:248 [inline] ip_rcv+0xc3f/0x17d0 net/ipv4/ip_input.c:488 __netif_receive_skb_core+0x1b05/0x3230 net/core/dev.c:4298 __netif_receive_skb+0x2c/0x1b0 net/core/dev.c:4336 netif_receive_skb_internal+0x16a/0x1a50 net/core/dev.c:4497 netif_receive_skb+0xae/0x390 net/core/dev.c:4521 tun_rx_batched.isra.42+0x5e7/0x860 drivers/net/tun.c:1167 tun_get_user+0xde5/0x2910 drivers/net/tun.c:1339 tun_chr_write_iter+0xd8/0x190 drivers/net/tun.c:1365 call_write_iter include/linux/fs.h:1743 [inline] new_sync_write fs/read_write.c:457 [inline] __vfs_write+0x684/0x970 fs/read_write.c:470 vfs_write+0x189/0x510 fs/read_write.c:518 SYSC_write fs/read_write.c:565 [inline] SyS_write+0xef/0x220 fs/read_write.c:557 entry_SYSCALL_64_fastpath+0x1f/0xbe RIP: 0033:0x405b41 RSP: 002b:00007f9d35b9bd90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000405b41 RDX: 0000000000000036 RSI: 0000000020002000 RDI: 0000000000000003 RBP: 0000000000000086 R08: 0000000000000013 R09: 00007f9d35b9c700 R10: 00007f9d35b9c9d0 R11: 0000000000000293 R12: 0000000000000000 R13: 00007fff21d63eef R14: 00007f9d35b9c9c0 R15: 0000000000000000 The buggy address belongs to the page: page:ffffea00065c6690 count:0 mapcount:0 mapping: (null) index:0xffff8801d141e7c0 flags: 0x200000000000000() raw: 0200000000000000 0000000000000000 ffff8801d141e7c0 00000000ffffffff raw: dead000000000100 dead000000000200 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8801d141e480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8801d141e500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff8801d141e580: 00 00 f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f3 f3 ^ ffff8801d141e600: f3 f3 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 ffff8801d141e680: 00 00 00 00 00 00 00 f2 f2 f3 f3 f3 f3 00 00 00 ==================================================================