[v6.6] WARNING in uprobe_unregister

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 147338df3487 Linux 6.6.108
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17bcfc14580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=cbe3f27f022f79f14611
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/23d0a7436789/disk-147338df.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5658c8bd0cce/vmlinux-147338df.xz
kernel image: https://storage.googleapis.com/syzbot-assets/be243abccdbe/bzImage-147338df.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cbe3f2...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6930 at kernel/events/uprobes.c:1123 uprobe_unregister+0x63/0x70 kernel/events/uprobes.c:1123
Modules linked in:
CPU: 0 PID: 6930 Comm: syz.2.230 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:uprobe_unregister+0x63/0x70 kernel/events/uprobes.c:1123
Code: e8 b2 14 c6 08 4c 89 f7 48 89 de e8 a7 01 00 00 4c 89 ff e8 6f 41 b5 ff 4c 89 f7 5b 41 5e 41 5f e9 72 03 00 00 e8 5d 68 d4 ff <0f> 0b 5b 41 5e 41 5f c3 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc9000447fc88 EFLAGS: 00010293
RAX: ffffffff81b12f43 RBX: ffff88802def0a20 RCX: ffff88802a2b3c00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 00000000ffffffff
RBP: ffff88802b985fb8 R08: ffffffff8cdd1da3 R09: 1ffffffff19ba3b4
R10: dffffc0000000000 R11: fffffbfff19ba3b5 R12: ffff888140109908
R13: ffff88802def0a20 R14: 0000000000000000 R15: ffff88802b985fb8
FS: 000055555847a500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e70aff8 CR3: 0000000067007000 CR4: 00000000003506f0
Call Trace:
<TASK>
bpf_uprobe_unregister kernel/trace/bpf_trace.c:3072 [inline]
bpf_uprobe_multi_link_release+0x134/0x2f0 kernel/trace/bpf_trace.c:3082
bpf_link_free+0x131/0x310 kernel/bpf/syscall.c:2918
bpf_link_put_direct kernel/bpf/syscall.c:2958 [inline]
bpf_link_release+0x6e/0x80 kernel/bpf/syscall.c:2965
__fput+0x234/0x970 fs/file_table.c:384
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f9f2338eec9
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff33df9338 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000025ea0 RCX: 00007f9f2338eec9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f9f235e7da0 R08: 0000000000000001 R09: 0000000a33df962f
R10: 0000001b2d520000 R11: 0000000000000246 R12: 00007f9f235e609c
R13: 00007fff33df9430 R14: ffffffffffffffff R15: 00007fff33df9450
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f34f16e5c632 Linux 6.6.109
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1705d942580000

kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=cbe3f27f022f79f14611
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10abaa7c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1d84cf343aca/disk-f34f16e5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/613ae177a403/vmlinux-f34f16e5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b9016970cbc/bzImage-f34f16e5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/92ea273f8b26/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cbe3f2...@syzkaller.appspotmail.com

------------[ cut here ]------------

WARNING: CPU: 1 PID: 6070 at kernel/events/uprobes.c:1123 uprobe_unregister+0x63/0x70 kernel/events/uprobes.c:1123
Modules linked in:
CPU: 1 PID: 6070 Comm: syz.1.54 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:uprobe_unregister+0x63/0x70 kernel/events/uprobes.c:1123

Code: e8 72 42 c6 08 4c 89 f7 48 89 de e8 a7 01 00 00 4c 89 ff e8 6f 42 b5 ff 4c 89 f7 5b 41 5e 41 5f e9 72 03 00 00 e8 5d 69 d4 ff <0f> 0b 5b 41 5e 41 5f c3 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc90003307c88 EFLAGS: 00010293
RAX: ffffffff81b12193 RBX: ffff88805dcfada0 RCX: ffff888018fe0000

RDX: 0000000000000000 RSI: 0000000000000004 RDI: 00000000ffffffff

RBP: ffff88802c37cb90 R08: ffffffff8cdd1ea3 R09: 1ffffffff19ba3d4
R10: dffffc0000000000 R11: fffffbfff19ba3d5 R12: ffff888021a82508
R13: ffff88805dcfada0 R14: 0000000000000000 R15: ffff88802c37cb90
FS: 000055556f966500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00002000000012c0 CR3: 0000000020507000 CR4: 00000000003506e0

Call Trace:
<TASK>
bpf_uprobe_unregister kernel/trace/bpf_trace.c:3072 [inline]
bpf_uprobe_multi_link_release+0x134/0x2f0 kernel/trace/bpf_trace.c:3082
bpf_link_free+0x131/0x310 kernel/bpf/syscall.c:2918
bpf_link_put_direct kernel/bpf/syscall.c:2958 [inline]
bpf_link_release+0x6e/0x80 kernel/bpf/syscall.c:2965
__fput+0x234/0x970 fs/file_table.c:384
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7f564678eec9

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 a8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007ffdc51f3ea8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f56469e7da0 RCX: 00007f564678eec9

RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003

RBP: 00007f56469e7da0 R08: 0000000000000000 R09: 00000009c51f419f
R10: 000000000003fd80 R11: 0000000000000246 R12: 000000000001a9d3
R13: 00007f56469e6090 R14: ffffffffffffffff R15: 00007ffdc51f3fc0
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.