audit: type=1400 audit(1766408277.675:73): avc: denied { read } for pid=5006 comm="syz-executor.7" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=perf_event permissive=1 loop1: detected capacity change from 0 to 64 FAT-fs (loop1): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) ====================================================== WARNING: possible circular locking dependency detected 6.19.0-rc1-next-20251219 #1 Not tainted ------------------------------------------------------ syz-executor.7/5009 is trying to acquire lock: ffffffff85e90a28 (event_mutex){+.+.}-{4:4}, at: perf_trace_destroy+0x27/0x1c0 but task is already holding lock: ffff888018be6540 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x159/0x390 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #6 (&mm->mmap_lock){++++}-{4:4}: __might_fault+0x110/0x190 _copy_from_user+0x2b/0xd0 memdup_user+0x7e/0xe0 strndup_user+0x78/0xe0 _perf_ioctl+0x4fc/0x21f0 perf_ioctl+0x74/0xb0 __x64_sys_ioctl+0x18f/0x210 do_syscall_64+0xbf/0x420 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #5 (&cpuctx_mutex){+.+.}-{4:4}: __mutex_lock+0x14e/0x2380 perf_event_init_cpu+0x302/0x760 perf_event_init+0x51b/0x730 start_kernel+0x267/0x510 x86_64_start_reservations+0x18/0x30 x86_64_start_kernel+0x109/0x120 common_startup_64+0x13e/0x148 -> #4 (pmus_lock){+.+.}-{4:4}: __mutex_lock+0x14e/0x2380 perf_event_init_cpu+0xc3/0x760 cpuhp_invoke_callback+0xa7c/0x13d0 cpuhp_thread_fun+0x41e/0x690 smpboot_thread_fn+0x41d/0x9d0 kthread+0x3c8/0x740 ret_from_fork+0x67a/0x7a0 ret_from_fork_asm+0x1a/0x30 -> #3 (cpuhp_state-up){+.+.}-{0:0}: cpuhp_thread_fun+0x14c/0x690 smpboot_thread_fn+0x41d/0x9d0 kthread+0x3c8/0x740 ret_from_fork+0x67a/0x7a0 ret_from_fork_asm+0x1a/0x30 -> #2 (cpu_hotplug_lock){++++}-{0:0}: cpus_read_lock+0x42/0x160 __static_call_update+0x8c/0x600 tracepoint_add_func+0xab9/0xec0 tracepoint_probe_register+0xa4/0xf0 trace_event_reg+0x2a8/0x370 perf_trace_event_init+0x511/0xa10 perf_trace_init+0x1a4/0x2f0 perf_tp_event_init+0xa6/0x120 perf_try_init_event+0x140/0x9f0 perf_event_alloc.part.0+0x1130/0x4640 __do_sys_perf_event_open+0x70b/0x2c20 do_syscall_64+0xbf/0x420 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (tracepoints_mutex){+.+.}-{4:4}: __mutex_lock+0x14e/0x2380 tracepoint_probe_register+0x7b/0xf0 trace_event_reg+0x2a8/0x370 perf_trace_event_init+0x511/0xa10 perf_trace_init+0x1a4/0x2f0 perf_tp_event_init+0xa6/0x120 perf_try_init_event+0x140/0x9f0 perf_event_alloc.part.0+0x1130/0x4640 __do_sys_perf_event_open+0x70b/0x2c20 do_syscall_64+0xbf/0x420 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (event_mutex){+.+.}-{4:4}: __lock_acquire+0x1275/0x2250 lock_acquire+0x15e/0x2d0 __mutex_lock+0x14e/0x2380 perf_trace_destroy+0x27/0x1c0 __free_event+0x255/0xc30 perf_mmap_close+0x7c1/0x11a0 __mmap_region+0x6f3/0x26e0 mmap_region+0x314/0x3e0 do_mmap+0xa36/0x11d0 vm_mmap_pgoff+0x1fc/0x390 ksys_mmap_pgoff+0x3d7/0x520 __x64_sys_mmap+0x127/0x190 do_syscall_64+0xbf/0x420 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: event_mutex --> &cpuctx_mutex --> &mm->mmap_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mm->mmap_lock); lock(&cpuctx_mutex); lock(&mm->mmap_lock); lock(event_mutex); *** DEADLOCK *** 1 lock held by syz-executor.7/5009: #0: ffff888018be6540 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x159/0x390 stack backtrace: CPU: 0 UID: 0 PID: 5009 Comm: syz-executor.7 Not tainted 6.19.0-rc1-next-20251219 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: dump_stack_lvl+0xca/0x120 print_circular_bug+0x2d7/0x410 check_noncircular+0x121/0x140 __lock_acquire+0x1275/0x2250 lock_acquire+0x15e/0x2d0 __mutex_lock+0x14e/0x2380 perf_trace_destroy+0x27/0x1c0 __free_event+0x255/0xc30 perf_mmap_close+0x7c1/0x11a0 __mmap_region+0x6f3/0x26e0 mmap_region+0x314/0x3e0 do_mmap+0xa36/0x11d0 vm_mmap_pgoff+0x1fc/0x390 ksys_mmap_pgoff+0x3d7/0x520 __x64_sys_mmap+0x127/0x190 do_syscall_64+0xbf/0x420 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fe07e1d1b19 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:00007fe07b747188 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007fe07e2e4f60 RCX: 00007fe07e1d1b19 RDX: 0000000000000000 RSI: 0000000000001000 RDI: 0000000020ffe000 RBP: 00007fe07e22bf6d R08: 0000000000000006 R09: 0000000000000000 R10: 0000000000000011 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff552f1bdf R14: 00007fe07b747300 R15: 0000000000022000 loop1: detected capacity change from 0 to 64 FAT-fs (loop1): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s sr 1:0:0:0: [sr0] tag#0 CDB: Read attributes 8c 6a 0e 56 7f e0 14 67 cb 03 45 31 loop1: detected capacity change from 0 to 64 FAT-fs (loop1): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) loop1: detected capacity change from 0 to 64 FAT-fs (loop1): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)