==================================================================
BUG: KASAN: stack-out-of-bounds in skb_splice_from_iter+0xcd6/0xd70 net/core/skbuff.c:6933
Read of size 8 at addr ffffc90004eaf8f8 by task syz-executor.2/7664

CPU: 1 PID: 7664 Comm: syz-executor.2 Not tainted 6.4.0-rc5-syzkaller-00915-ge7c5433c5aaa #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:351
 print_report mm/kasan/report.c:462 [inline]
 kasan_report+0x11c/0x130 mm/kasan/report.c:572
 skb_splice_from_iter+0xcd6/0xd70 net/core/skbuff.c:6933
 __ip_append_data+0x1439/0x3c20 net/ipv4/ip_output.c:1210
 ip_append_data net/ipv4/ip_output.c:1350 [inline]
 ip_append_data+0x115/0x1a0 net/ipv4/ip_output.c:1329
 raw_sendmsg+0xb50/0x30a0 net/ipv4/raw.c:641
 inet_sendmsg+0x9d/0xe0 net/ipv4/af_inet.c:829
 sock_sendmsg_nosec net/socket.c:724 [inline]
 sock_sendmsg+0xde/0x190 net/socket.c:747
 splice_to_socket+0x954/0xe30 fs/splice.c:917
 do_splice_from fs/splice.c:969 [inline]
 do_splice+0xb8c/0x1e50 fs/splice.c:1309
 __do_splice+0x14e/0x270 fs/splice.c:1387
 __do_sys_splice fs/splice.c:1598 [inline]
 __se_sys_splice fs/splice.c:1580 [inline]
 __x64_sys_splice+0x19c/0x250 fs/splice.c:1580
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbd1ba8c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbd1c87b168 EFLAGS: 00000246 ORIG_RAX: 0000000000000113
RAX: ffffffffffffffda RBX: 00007fbd1bbabf80 RCX: 00007fbd1ba8c169
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007fbd1bae7ca1 R08: 0000000000000005 R09: 0000000000000005
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdbe0d8ebf R14: 00007fbd1c87b300 R15: 0000000000022000
 </TASK>

The buggy address belongs to stack of task syz-executor.2/7664
 and is located at offset 408 in frame:
 raw_sendmsg+0x0/0x30a0 include/net/sock.h:2733

This frame has 8 objects:
 [48, 52) 'hdrincl'
 [64, 68) 'err'
 [80, 88) 'rt'
 [112, 152) 'ipc'
 [192, 240) 'state'
 [272, 336) 'fl4'
 [368, 392) 'rfv'
 [432, 504) 'opt_copy'

The buggy address belongs to the virtual mapping at
 [ffffc90004ea8000, ffffc90004eb1000) created by:
 kernel_clone+0xeb/0x890 kernel/fork.c:2915

The buggy address belongs to the physical page:
page:ffffea0000833040 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20cc1
memcg:ffff888075dcc382
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888075dcc382
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 51, tgid 51 (kworker/u4:3), ts 211887150452, free_ts 204579629196
 set_page_owner include/linux/page_owner.h:31 [inline]
 post_alloc_hook+0x2db/0x350 mm/page_alloc.c:1731
 prep_new_page mm/page_alloc.c:1738 [inline]
 get_page_from_freelist+0xf41/0x2c00 mm/page_alloc.c:3502
 __alloc_pages+0x1cb/0x4a0 mm/page_alloc.c:4768
 alloc_pages+0x1aa/0x270 mm/mempolicy.c:2279
 vm_area_alloc_pages mm/vmalloc.c:3009 [inline]
 __vmalloc_area_node mm/vmalloc.c:3085 [inline]
 __vmalloc_node_range+0xb1c/0x14a0 mm/vmalloc.c:3257
 alloc_thread_stack_node kernel/fork.c:313 [inline]
 dup_task_struct kernel/fork.c:1116 [inline]
 copy_process+0x13bb/0x75c0 kernel/fork.c:2333
 kernel_clone+0xeb/0x890 kernel/fork.c:2915
 user_mode_thread+0xb1/0xf0 kernel/fork.c:2993
 call_usermodehelper_exec_sync kernel/umh.c:133 [inline]
 call_usermodehelper_exec_work+0x6d/0x180 kernel/umh.c:164
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1302 [inline]
 free_unref_page_prepare+0x62e/0xcb0 mm/page_alloc.c:2564
 free_unref_page+0x33/0x370 mm/page_alloc.c:2659
 vfree+0x180/0x7e0 mm/vmalloc.c:2798
 kvfree+0x32/0x50 mm/util.c:648
 prealloc_init kernel/bpf/hashtab.c:368 [inline]
 htab_map_alloc+0x1043/0x1640 kernel/bpf/hashtab.c:566
 find_and_alloc_map kernel/bpf/syscall.c:135 [inline]
 map_create+0x508/0x1860 kernel/bpf/syscall.c:1161
 __sys_bpf+0x1478/0x54b0 kernel/bpf/syscall.c:5072
 __do_sys_bpf kernel/bpf/syscall.c:5194 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:5192 [inline]
 __x64_sys_bpf+0x79/0xc0 kernel/bpf/syscall.c:5192
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
 ffffc90004eaf780: f1 f1 04 f2 00 00 00 f2 f2 f2 00 00 00 00 00 f2
 ffffc90004eaf800: f2 f2 f2 f2 00 00 00 00 00 00 f2 f2 f2 f2 00 00
>ffffc90004eaf880: 00 00 00 00 00 00 f2 f2 f2 f2 00 00 00 f2 f2 f2
                                                                ^
 ffffc90004eaf900: f2 f2 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3 f3
 ffffc90004eaf980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================