================================================================== BUG: KASAN: stack-out-of-bounds in _copy_to_iter+0x48f/0x1420 Read of size 4095 at addr ffff888040c47b11 by task syz-executor.0/7965 CPU: 0 PID: 7965 Comm: syz-executor.0 Not tainted 5.19.0-rc6-next-20220711 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x8b/0xb3 print_report.cold+0x5e/0x5e1 kasan_report+0xb1/0x1b0 kasan_check_range+0x35/0x1b0 memcpy+0x20/0x60 _copy_to_iter+0x48f/0x1420 tty_read+0x29a/0x5d0 generic_file_splice_read+0x187/0x4d0 do_splice_to+0x1bc/0x240 splice_file_to_pipe+0x100/0x120 do_sendfile+0x42a/0x1270 __x64_sys_sendfile64+0x1cd/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7ff3423c9b19 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ff33f93f188 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007ff3424dcf60 RCX: 00007ff3423c9b19 RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004 RBP: 00007ff342423f6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffb9dcce5f R14: 00007ff33f93f300 R15: 0000000000022000 The buggy address belongs to stack of task syz-executor.0/7965 and is located at offset 65 in frame: tty_read+0x0/0x5d0 This frame has 2 objects: [32, 40) 'cookie' [64, 128) 'kernel_buf' The buggy address belongs to the physical page: page:00000000ed9e158e refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x40c47 flags: 0x100000000000000(node=0|zone=1) raw: 0100000000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888040c47a00: 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 ffff888040c47a80: 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f2 >ffff888040c47b00: f2 f2 00 00 00 00 00 00 00 00 f3 f3 f3 f3 00 00 ^ ffff888040c47b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 ffff888040c47c00: f1 f1 f1 00 00 00 00 00 f2 f2 f2 f2 f2 00 00 00 ================================================================== ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy0 wpan0: encryption failed: -22 loop2: detected capacity change from 0 to 40 loop2: detected capacity change from 0 to 40 loop2: detected capacity change from 0 to 40 loop2: detected capacity change from 0 to 40 9pnet_fd: p9_fd_create_tcp (8094): problem connecting socket to 127.0.0.1 9pnet_fd: p9_fd_create_tcp (8115): problem connecting socket to 127.0.0.1 9pnet_fd: p9_fd_create_tcp (8132): problem connecting socket to 127.0.0.1 loop2: detected capacity change from 0 to 256 FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) 9pnet_fd: p9_fd_create_tcp (8187): problem connecting socket to 127.0.0.1 loop2: detected capacity change from 0 to 256 FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) loop2: detected capacity change from 0 to 256 FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) 9pnet_fd: p9_fd_create_tcp (8224): problem connecting socket to 127.0.0.1 warning: checkpointing journal with EXT4_IOC_CHECKPOINT_FLAG_ZEROOUT can be slow