[moderation] [perf?] general protection fault in perf_tp_event (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f14cdb1367b9 Merge branch 'remove-kf_sleepable-from-arena-..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1388c89a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4aa52bacc0658d1
dashboard link: https://syzkaller.appspot.com/bug?extid=ab9f25283e0ce0023789
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
CC: [ac...@kernel.org adrian...@intel.com alexander...@linux.intel.com iro...@google.com james...@linaro.org jo...@kernel.org linux-...@vger.kernel.org linux-pe...@vger.kernel.org mark.r...@arm.com mi...@redhat.com namh...@kernel.org net...@vger.kernel.org pet...@infradead.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f66f6c348249/disk-f14cdb13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9452d144ea2e/vmlinux-f14cdb13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3356b2b3987c/bzImage-f14cdb13.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000037: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x00000000000001b8-0x00000000000001bf]
CPU: 1 UID: 0 PID: 16195 Comm: napi/wg0-0 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:perf_tp_event_match kernel/events/core.c:10979 [inline]
RIP: 0010:perf_tp_event+0x163/0x1380 kernel/events/core.c:11070
Code: 24 80 00 00 00 4c 8d 68 08 48 83 c0 50 48 89 44 24 28 4c 89 6c 24 18 4c 89 34 24 49 8d 9c 24 f8 01 00 00 48 89 d8 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 f5 03 00 00 8b 1b 89 de 83 e6 01 31 ff
RSP: 0018:ffffc9000402f200 EFLAGS: 00010002
RAX: 0000000000000037 RBX: 00000000000001b8 RCX: 0000000000000001
RDX: ffff88801cf2bd00 RSI: 0000000080000202 RDI: ffffe8ffff76e004
RBP: ffffc9000402f468 R08: ffffc9000402f3cf R09: 0000000000000000
R10: ffffc9000402f3c0 R11: fffff52000805e7a R12: ffffffffffffffc0
R13: ffffc9000402f288 R14: ffff8880b8733178 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888125f34000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555575e24588 CR3: 000000001e784000 CR4: 00000000003526f0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
perf_trace_run_bpf_submit+0xee/0x170 kernel/events/core.c:11005
do_perf_trace_lock include/trace/events/lock.h:50 [inline]
perf_trace_lock+0x2f8/0x3b0 include/trace/events/lock.h:50
__do_trace_lock_release include/trace/events/lock.h:69 [inline]
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0x389/0x3b0 kernel/locking/lockdep.c:5879
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:149 [inline]
_raw_spin_unlock_irqrestore+0x70/0x110 kernel/locking/spinlock.c:194
__debug_check_no_obj_freed lib/debugobjects.c:1108 [inline]
debug_check_no_obj_freed+0x52e/0x550 lib/debugobjects.c:1129
slab_free_hook mm/slub.c:2471 [inline]
slab_free mm/slub.c:6668 [inline]
kmem_cache_free+0x110/0x620 mm/slub.c:6779
skb_release_data+0x62d/0x7c0 net/core/skbuff.c:1107
skb_release_all net/core/skbuff.c:1182 [inline]
__kfree_skb net/core/skbuff.c:1196 [inline]
consume_skb+0x9e/0xf0 net/core/skbuff.c:1428
wg_packet_consume_data_done drivers/net/wireguard/receive.c:435 [inline]
wg_packet_rx_poll+0x14c3/0x24a0 drivers/net/wireguard/receive.c:474
__napi_poll+0xae/0x320 net/core/dev.c:7666
napi_threaded_poll_loop+0x374/0x7a0 net/core/dev.c:7785
napi_threaded_poll+0x29d/0x3c0 net/core/dev.c:7836
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:perf_tp_event_match kernel/events/core.c:10979 [inline]
RIP: 0010:perf_tp_event+0x163/0x1380 kernel/events/core.c:11070
Code: 24 80 00 00 00 4c 8d 68 08 48 83 c0 50 48 89 44 24 28 4c 89 6c 24 18 4c 89 34 24 49 8d 9c 24 f8 01 00 00 48 89 d8 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 f5 03 00 00 8b 1b 89 de 83 e6 01 31 ff
RSP: 0018:ffffc9000402f200 EFLAGS: 00010002
RAX: 0000000000000037 RBX: 00000000000001b8 RCX: 0000000000000001
RDX: ffff88801cf2bd00 RSI: 0000000080000202 RDI: ffffe8ffff76e004
RBP: ffffc9000402f468 R08: ffffc9000402f3cf R09: 0000000000000000
R10: ffffc9000402f3c0 R11: fffff52000805e7a R12: ffffffffffffffc0
R13: ffffc9000402f288 R14: ffff8880b8733178 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888125f34000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555575e24588 CR3: 000000001e784000 CR4: 00000000003526f0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
----------------
Code disassembly (best guess):
0: 24 80 and $0x80,%al
2: 00 00 add %al,(%rax)
4: 00 4c 8d 68 add %cl,0x68(%rbp,%rcx,4)
8: 08 48 83 or %cl,-0x7d(%rax)
b: c0 50 48 89 rclb $0x89,0x48(%rax)
f: 44 24 28 rex.R and $0x28,%al
12: 4c 89 6c 24 18 mov %r13,0x18(%rsp)
17: 4c 89 34 24 mov %r14,(%rsp)
1b: 49 8d 9c 24 f8 01 00 lea 0x1f8(%r12),%rbx
22: 00
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 38 movzbl (%rax,%r15,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 f5 03 00 00 jne 0x42c
37: 8b 1b mov (%rbx),%ebx
39: 89 de mov %ebx,%esi
3b: 83 e6 01 and $0x1,%esi
3e: 31 ff xor %edi,%edi


---
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