kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: 0000 [#1] PREEMPT SMP KASAN audit: type=1400 audit(1569001886.917:42): avc: denied { map } for pid=6934 comm="syz-executor.3" path="/root/syzkaller-testdir372236881/syzkaller.UrQ65E/12/file0/mem" dev="devtmpfs" ino=13680 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=system_u:object_r:memory_device_t:s0 tclass=chr_file permissive=1 Modules linked in: CPU: 0 PID: 6926 Comm: syz-executor.4 Not tainted 4.14.145 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 protocol 88fb is buggy, dev hsr_slave_0 task: ffff88808e55e3c0 task.stack: ffff88808dc30000 protocol 88fb is buggy, dev hsr_slave_1 RIP: 0010:tcp_sendmsg_locked+0x50e/0x3200 net/ipv4/tcp.c:1281 RSP: 0018:ffff88808dc379b0 EFLAGS: 00010206 RAX: 0000000000000012 RBX: 0000000000000000 RCX: ffffc9000984a000 RDX: 000000000000011c RSI: ffffffff85240e44 RDI: 0000000000000090 RBP: ffff88808dc37b48 R08: ffff88808e55e3c0 R09: 0000000000000001 R10: 0000000000000000 R11: ffff88808e55e3c0 R12: dffffc0000000000 R13: ffff888096982800 R14: ffff88808dc37c28 R15: ffff8880a925c040 FS: 00007fad3d4bf700(0000) GS:ffff8880aee00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffdf149b6e0 CR3: 00000000a8d41000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: tcp_sendmsg+0x30/0x50 net/ipv4/tcp.c:1457 inet_sendmsg+0x122/0x500 net/ipv4/af_inet.c:762 sock_sendmsg_nosec net/socket.c:646 [inline] sock_sendmsg+0xce/0x110 net/socket.c:656 sock_write_iter+0x21d/0x390 net/socket.c:925 call_write_iter include/linux/fs.h:1777 [inline] new_sync_write fs/read_write.c:469 [inline] __vfs_write+0x4a7/0x6b0 fs/read_write.c:482 vfs_write+0x198/0x500 fs/read_write.c:544 SYSC_write fs/read_write.c:590 [inline] SyS_write+0xfd/0x230 fs/read_write.c:582 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x459a09 RSP: 002b:00007fad3d4bec78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459a09 RDX: 0000000000000001 RSI: 0000000020000140 RDI: 0000000000000004 RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fad3d4bf6d4 R13: 00000000004c5f88 R14: 00000000004e0610 R15: 00000000ffffffff Code: d4 38 fc 4d 85 ed 0f 84 40 08 00 00 e8 ac d4 38 fc 8b 85 78 ff ff ff 48 8d bb 90 00 00 00 89 85 50 ff ff ff 48 89 f8 48 c1 e8 03 <42> 0f b6 04 20 84 c0 74 06 0f 8e 4a 25 00 00 f6 83 90 00 00 00 RIP: tcp_sendmsg_locked+0x50e/0x3200 net/ipv4/tcp.c:1281 RSP: ffff88808dc379b0 L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. ---[ end trace ef907ad3216e346f ]---