================================================================== BUG: KASAN: stack-out-of-bounds in __get_unaligned_cpu32 include/linux/unaligned/packed_struct.h:19 [inline] BUG: KASAN: stack-out-of-bounds in jhash+0x200/0x740 include/linux/jhash.h:82 Read of size 4 at addr ffffc900032a71a0 by task syz-executor.1/7543 CPU: 0 PID: 7543 Comm: syz-executor.1 Not tainted 6.8.0-syzkaller-05236-g443574b03387 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __get_unaligned_cpu32 include/linux/unaligned/packed_struct.h:19 [inline] jhash+0x200/0x740 include/linux/jhash.h:82 hash+0x339/0x410 kernel/bpf/bloom_filter.c:31 bloom_map_peek_elem+0xb2/0x1b0 kernel/bpf/bloom_filter.c:43 bpf_prog_00798911c748094f+0x42/0x46 bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline] __bpf_prog_run include/linux/filter.h:657 [inline] bpf_prog_run include/linux/filter.h:664 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2381 [inline] bpf_trace_run3+0x238/0x460 kernel/trace/bpf_trace.c:2421 trace_ext4_da_write_pages include/trace/events/ext4.h:486 [inline] ext4_do_writepages+0x3254/0x3ca0 fs/ext4/inode.c:2676 ext4_writepages+0x204/0x3e0 fs/ext4/inode.c:2768 do_writepages+0x3a4/0x670 mm/page-writeback.c:2553 filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:388 __filemap_fdatawrite_range mm/filemap.c:421 [inline] file_write_and_wait_range+0x20f/0x300 mm/filemap.c:779 ext4_sync_file+0x250/0xb50 fs/ext4/fsync.c:158 generic_write_sync include/linux/fs.h:2793 [inline] ext4_buffered_write_iter+0x286/0x350 fs/ext4/file.c:305 ext4_file_write_iter+0x1de/0x1a10 call_write_iter include/linux/fs.h:2108 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0xa84/0xcb0 fs/read_write.c:590 ksys_write+0x1a0/0x2c0 fs/read_write.c:643 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7ff1bc07de69 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ff1bcde10c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007ff1bc1ac050 RCX: 00007ff1bc07de69 RDX: 0000000000002000 RSI: 0000000020000180 RDI: 000000000000000b RBP: 00007ff1bc0ca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007ff1bc1ac050 R15: 00007ffe606d1798 The buggy address belongs to stack of task syz-executor.1/7543 and is located at offset 0 in frame: bpf_trace_run3+0x0/0x460 This frame has 1 object: [32, 56) 'args' The buggy address belongs to the virtual mapping at [ffffc900032a0000, ffffc900032a9000) created by: copy_process+0x5d1/0x3df0 kernel/fork.c:2219 The buggy address belongs to the physical page: page:ffffea00008e4f00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2393c memcg:ffff88802b093d02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88802b093d02 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 7378, tgid 7378 (syz-executor.0), ts 146598376898, free_ts 145461710293 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x1ea/0x210 mm/page_alloc.c:1533 prep_new_page mm/page_alloc.c:1540 [inline] get_page_from_freelist+0x33ea/0x3580 mm/page_alloc.c:3311 __alloc_pages+0x256/0x680 mm/page_alloc.c:4569 alloc_pages_mpol+0x3de/0x650 mm/mempolicy.c:2133 vm_area_alloc_pages mm/vmalloc.c:3135 [inline] __vmalloc_area_node mm/vmalloc.c:3211 [inline] __vmalloc_node_range+0x9a4/0x14a0 mm/vmalloc.c:3392 alloc_thread_stack_node kernel/fork.c:309 [inline] dup_task_struct+0x3e9/0x7d0 kernel/fork.c:1114 copy_process+0x5d1/0x3df0 kernel/fork.c:2219 kernel_clone+0x21e/0x8d0 kernel/fork.c:2796 __do_sys_clone3 kernel/fork.c:3097 [inline] __se_sys_clone3+0x2cb/0x350 kernel/fork.c:3081 do_syscall_64+0xfb/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 page last free pid 5128 tgid 5128 stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1140 [inline] free_unref_page_prepare+0x968/0xa90 mm/page_alloc.c:2346 free_unref_page+0x37/0x3f0 mm/page_alloc.c:2486 kasan_depopulate_vmalloc_pte+0x74/0x90 mm/kasan/shadow.c:415 apply_to_pte_range mm/memory.c:2619 [inline] apply_to_pmd_range mm/memory.c:2663 [inline] apply_to_pud_range mm/memory.c:2699 [inline] apply_to_p4d_range mm/memory.c:2735 [inline] __apply_to_page_range+0x8ec/0xe40 mm/memory.c:2769 kasan_release_vmalloc+0x9a/0xb0 mm/kasan/shadow.c:532 __purge_vmap_area_lazy+0x163f/0x1a10 mm/vmalloc.c:1842 drain_vmap_area_work+0x40/0xd0 mm/vmalloc.c:1876 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa00/0x1770 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f0/0x390 kernel/kthread.c:388 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243 Memory state around the buggy address: ffffc900032a7080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900032a7100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900032a7180: 00 00 00 00 f1 f1 f1 f1 00 00 00 f3 f3 f3 f3 f3 ^ ffffc900032a7200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900032a7280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================