==================================================================
BUG: KASAN: stack-out-of-bounds in fixup_exception+0xa7/0x1cc0 arch/x86/mm/extable.c:320
Read of size 8 at addr ffffc900178bfac8 by task syz.0.120/6076

CPU: 0 UID: 0 PID: 6076 Comm: syz.0.120 Not tainted 6.11.0-rc4-next-20240820-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:

The buggy address belongs to the virtual mapping at
 [ffffc900178b8000, ffffc900178c1000) created by:
 copy_process+0x5d1/0x3d50 kernel/fork.c:2206

The buggy address belongs to the physical page:
page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x69ac2
memcg:ffff88801f4a2f02
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88801f4a2f02
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 5794, tgid 5794 (syz-executor), ts 165188141684, free_ts 165183304676
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1517
 prep_new_page mm/page_alloc.c:1525 [inline]
 get_page_from_freelist+0x3004/0x30c0 mm/page_alloc.c:3476
 __alloc_pages_noprof+0x29e/0x780 mm/page_alloc.c:4743
 alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265
 vm_area_alloc_pages mm/vmalloc.c:3600 [inline]
 __vmalloc_area_node mm/vmalloc.c:3669 [inline]
 __vmalloc_node_range_noprof+0xa40/0x1400 mm/vmalloc.c:3850
 alloc_thread_stack_node kernel/fork.c:314 [inline]
 dup_task_struct+0x444/0x8c0 kernel/fork.c:1115
 copy_process+0x5d1/0x3d50 kernel/fork.c:2206
 kernel_clone+0x226/0x8f0 kernel/fork.c:2787
 __do_sys_clone kernel/fork.c:2930 [inline]
 __se_sys_clone kernel/fork.c:2914 [inline]
 __x64_sys_clone+0x258/0x2a0 kernel/fork.c:2914
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 5786 tgid 5786 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1098 [inline]
 free_unref_page+0xc07/0xd90 mm/page_alloc.c:2651
 vfree+0x186/0x2e0 mm/vmalloc.c:3380
 kcov_put kernel/kcov.c:439 [inline]
 kcov_close+0x2b/0x50 kernel/kcov.c:535
 __fput+0x24b/0x890 fs/file_table.c:424
 task_work_run+0x24f/0x310 kernel/task_work.c:228
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0xa2f/0x28e0 kernel/exit.c:939
 do_group_exit+0x207/0x2c0 kernel/exit.c:1088
 __do_sys_exit_group kernel/exit.c:1099 [inline]
 __se_sys_exit_group kernel/exit.c:1097 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097
 x64_sys_call+0x26a8/0x26b0 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffffc900178bf980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc900178bfa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc900178bfa80: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 00 00 f2
                                              ^
 ffffc900178bfb00: f2 f2 f2 f2 04 f2 00 f2 f2 f2 00 00 f3 f3 f3 f3
 ffffc900178bfb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================