kernel tried to execute NX-protected page - exploit attempt? (uid: 0) BUG: unable to handle page fault for address: ffff88802c30c700 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0011) - permissions violation PGD 15401067 P4D 15401067 PUD 15402067 PMD 800000002c2000e3 Oops: Oops: 0011 [#1] PREEMPT SMP KASAN PTI CPU: 0 UID: 0 PID: 5403 Comm: syz.4.19 Not tainted 6.11.0-rc4-next-20240820-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:pv_wait arch/x86/include/asm/paravirt.h:596 [inline] RIP: 0010:pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:466 [inline] RIP: 0010:__pv_queued_spin_lock_slowpath+0x8d0/0xdb0 kernel/locking/qspinlock.c:508 Code: 00 74 0c 48 c7 c7 b8 45 7a 8e e8 7b 03 37 f6 48 83 3d 8b 03 b5 02 00 0f 84 e5 04 00 00 be 03 00 00 00 4c 89 f7 e8 a0 32 7b f5 <90> e9 4b fe ff ff 48 8b 4c 24 28 80 e1 07 38 c1 0f 8c 4d fe ff ff RSP: ea40:1ffff11017207d48 EFLAGS: 00010046 ORIG_RAX: ffffc900047df918 RAX: 1ffff920008fbf12 RBX: ce73286fd81ef000 RCX: ffff8880b903ea41 RDX: dffffc0000000000 RSI: ffff8880b903ea40 RDI: ffffc900047df8a0 ================================================================== BUG: KASAN: stack-out-of-bounds in __show_regs+0x172/0x610 arch/x86/kernel/process_64.c:87 Read of size 8 at addr ffffc900047df778 by task syz.4.19/5403 CPU: 0 UID: 0 PID: 5403 Comm: syz.4.19 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: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 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 __show_regs+0x172/0x610 arch/x86/kernel/process_64.c:87 show_regs arch/x86/kernel/dumpstack.c:472 [inline] __die_body+0x3c/0xb0 arch/x86/kernel/dumpstack.c:420 page_fault_oops+0x8e4/0xcc0 arch/x86/mm/fault.c:711 __bad_area_nosemaphore+0x118/0x770 arch/x86/mm/fault.c:785 The buggy address belongs to stack of task syz.4.19/5403 and is located at offset 88 in frame: kvm_wait+0x0/0x2c0 This frame has 2 objects: [32, 40) 'flags.i.i.i' [64, 72) 'flags.i.i' The buggy address belongs to the virtual mapping at [ffffc900047d8000, ffffc900047e1000) 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:0x5ea28 memcg:ffff888149a49d82 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888149a49d82 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 5343, tgid 5343 (syz.2.3), ts 63456199764, free_ts 12332906787 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_clone3 kernel/fork.c:3091 [inline] __se_sys_clone3+0x2cb/0x350 kernel/fork.c:3070 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 1 tgid 1 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 free_contig_range+0x152/0x550 mm/page_alloc.c:6758 destroy_args+0x8a/0x890 mm/debug_vm_pgtable.c:1017 debug_vm_pgtable+0x4be/0x550 mm/debug_vm_pgtable.c:1397 do_one_initcall+0x248/0x880 init/main.c:1267 do_initcall_level+0x157/0x210 init/main.c:1329 do_initcalls+0x3f/0x80 init/main.c:1345 kernel_init_freeable+0x435/0x5d0 init/main.c:1578 kernel_init+0x1d/0x2b0 init/main.c:1467 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Memory state around the buggy address: ffffc900047df600: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 ffffc900047df680: 00 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900047df700: 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2 00 f3 f3 f3 ^ ffffc900047df780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900047df800: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 ================================================================== ---------------- Code disassembly (best guess): 0: 00 74 0c 48 add %dh,0x48(%rsp,%rcx,1) 4: c7 c7 b8 45 7a 8e mov $0x8e7a45b8,%edi a: e8 7b 03 37 f6 call 0xf637038a f: 48 83 3d 8b 03 b5 02 cmpq $0x0,0x2b5038b(%rip) # 0x2b503a2 16: 00 17: 0f 84 e5 04 00 00 je 0x502 1d: be 03 00 00 00 mov $0x3,%esi 22: 4c 89 f7 mov %r14,%rdi 25: e8 a0 32 7b f5 call 0xf57b32ca * 2a: 90 nop <-- trapping instruction 2b: e9 4b fe ff ff jmp 0xfffffe7b 30: 48 8b 4c 24 28 mov 0x28(%rsp),%rcx 35: 80 e1 07 and $0x7,%cl 38: 38 c1 cmp %al,%cl 3a: 0f 8c 4d fe ff ff jl 0xfffffe8d