Hello,
syzbot found the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=164beab4580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link:
https://syzkaller.appspot.com/bug?extid=3af6f74a5ba50ad4b13d
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=1546301a580000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=143c3192580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/0d8305ca1c94/disk-f6e38ae6.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/8bc85383c07b/vmlinux-f6e38ae6.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/d337081bce56/bzImage-f6e38ae6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3af6f7...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {INITIAL USE} -> {IN-NMI} usage.
syz.0.17/4424 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff88802aec1238 (&trie->lock){....}-{2:2}, at: trie_delete_elem+0x90/0x690 kernel/bpf/lpm_trie.c:467
{INITIAL USE} state was registered at:
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
trie_delete_elem+0x90/0x690 kernel/bpf/lpm_trie.c:467
bpf_prog_0094bb5c89a0e79b+0x40/0x44
bpf_dispatcher_nop_func include/linux/bpf.h:1012 [inline]
__bpf_prog_run include/linux/filter.h:603 [inline]
bpf_prog_run include/linux/filter.h:610 [inline]
bpf_overflow_handler+0x525/0x7b0 kernel/events/core.c:10286
__perf_event_overflow+0x448/0x610 kernel/events/core.c:9496
perf_swevent_overflow kernel/events/core.c:9572 [inline]
perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9610
perf_bp_event+0x23a/0x2a0 kernel/events/core.c:10478
hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
notifier_call_chain kernel/notifier.c:87 [inline]
atomic_notifier_call_chain+0x17a/0x2b0 kernel/notifier.c:225
notify_die+0x12d/0x180 kernel/notifier.c:593
notify_debug+0x20/0x30 arch/x86/kernel/traps.c:1018
exc_debug_user arch/x86/kernel/traps.c:1144 [inline]
noist_exc_debug+0x73/0x120 arch/x86/kernel/traps.c:1181
asm_exc_debug+0x2f/0x40 arch/x86/include/asm/idtentry.h:648
irq event stamp: 2574
hardirqs last enabled at (2573): [<ffffffff8a17a5c0>] exc_debug_kernel arch/x86/kernel/traps.c:1093 [inline]
hardirqs last enabled at (2573): [<ffffffff8a17a5c0>] exc_debug+0xf0/0x130 arch/x86/kernel/traps.c:1175
hardirqs last disabled at (2574): [<ffffffff8a17a53e>] exc_debug_kernel arch/x86/kernel/traps.c:1039 [inline]
hardirqs last disabled at (2574): [<ffffffff8a17a53e>] exc_debug+0x6e/0x130 arch/x86/kernel/traps.c:1175
softirqs last enabled at (2276): [<ffffffff818f072f>] bpf_prog_load+0x117f/0x15a0 kernel/bpf/syscall.c:2674
softirqs last disabled at (2274): [<ffffffff818d4a79>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (2274): [<ffffffff818d4a79>] bpf_ksym_add+0x29/0x340 kernel/bpf/core.c:649
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&trie->lock);
<Interrupt>
lock(&trie->lock);
*** DEADLOCK ***
no locks held by syz.0.17/4424.
stack backtrace:
CPU: 0 PID: 4424 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<#DB>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
lock_acquire+0x2ce/0x490 kernel/locking/lockdep.c:5653
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
trie_delete_elem+0x90/0x690 kernel/bpf/lpm_trie.c:467
bpf_prog_0094bb5c89a0e79b+0x40/0x44
bpf_dispatcher_nop_func include/linux/bpf.h:1012 [inline]
__bpf_prog_run include/linux/filter.h:603 [inline]
bpf_prog_run include/linux/filter.h:610 [inline]
bpf_overflow_handler+0x525/0x7b0 kernel/events/core.c:10286
__perf_event_overflow+0x448/0x610 kernel/events/core.c:9496
perf_swevent_overflow kernel/events/core.c:9572 [inline]
perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9610
perf_bp_event+0x23a/0x2a0 kernel/events/core.c:10478
hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
notifier_call_chain kernel/notifier.c:87 [inline]
atomic_notifier_call_chain+0x17a/0x2b0 kernel/notifier.c:225
notify_die+0x12d/0x180 kernel/notifier.c:593
notify_debug+0x20/0x30 arch/x86/kernel/traps.c:1018
exc_debug_kernel arch/x86/kernel/traps.c:1075 [inline]
exc_debug+0xd9/0x130 arch/x86/kernel/traps.c:1175
asm_exc_debug+0x1a/0x40 arch/x86/include/asm/idtentry.h:648
RIP: 0010:copy_user_enhanced_fast_string+0xa/0x40 arch/x86/lib/copy_user_64.S:166
Code: ff c9 75 f2 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 31 c0 0f 01 ca c3 8d 0c ca 89 ca eb 20 0f 01 cb 83 fa 40 72 38 89 d1 <f3> a4 31 c0 0f 01 ca c3 89 ca eb 0a 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900032e7c28 EFLAGS: 00050206
RAX: ffffffff84072901 RBX: 0000000000000e40 RCX: 0000000000000dfd
RDX: 0000000000000e40 RSI: 0000200000000303 RDI: ffff888079fbc083
RBP: 0000000000000000 R08: dffffc0000000000 R09: ffffed100f3f79d0
R10: 0000000000000000 R11: 00000000000001c8 R12: 00007fffffffe1c0
R13: dffffc0000000000 R14: ffff888079fbc040 R15: 00002000000002c0
</#DB>
<TASK>
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_from_user arch/x86/include/asm/uaccess_64.h:52 [inline]
_copy_from_user+0xf4/0x170 lib/usercopy.c:23
copy_from_user include/linux/uaccess.h:161 [inline]
bpf_test_init net/bpf/test_run.c:779 [inline]
bpf_prog_test_run_skb+0x258/0x11b0 net/bpf/test_run.c:1100
bpf_prog_test_run+0x31e/0x390 kernel/bpf/syscall.c:3692
__sys_bpf+0x593/0x6d0 kernel/bpf/syscall.c:5045
__do_sys_bpf kernel/bpf/syscall.c:5131 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5129 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5129
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f62bb18f749
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:00007ffec3f8a6e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f62bb3e5fa0 RCX: 00007f62bb18f749
RDX: 000000000000004c RSI: 0000200000000240 RDI: 000000000000000a
RBP: 00007f62bb213f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f62bb3e5fa0 R14: 00007f62bb3e5fa0 R15: 0000000000000003
</TASK>
----------------
Code disassembly (best guess):
0: ff c9 dec %ecx
2: 75 f2 jne 0xfffffff6
4: 89 d1 mov %edx,%ecx
6: c1 e9 03 shr $0x3,%ecx
9: 83 e2 07 and $0x7,%edx
c: f3 48 a5 rep movsq %ds:(%rsi),%es:(%rdi)
f: 89 d1 mov %edx,%ecx
11: f3 a4 rep movsb %ds:(%rsi),%es:(%rdi)
13: 31 c0 xor %eax,%eax
15: 0f 01 ca clac
18: c3 ret
19: 8d 0c ca lea (%rdx,%rcx,8),%ecx
1c: 89 ca mov %ecx,%edx
1e: eb 20 jmp 0x40
20: 0f 01 cb stac
23: 83 fa 40 cmp $0x40,%edx
26: 72 38 jb 0x60
28: 89 d1 mov %edx,%ecx
* 2a: f3 a4 rep movsb %ds:(%rsi),%es:(%rdi) <-- trapping instruction
2c: 31 c0 xor %eax,%eax
2e: 0f 01 ca clac
31: c3 ret
32: 89 ca mov %ecx,%edx
34: eb 0a jmp 0x40
36: 90 nop
37: 90 nop
38: 90 nop
39: 90 nop
3a: 90 nop
3b: 90 nop
3c: 90 nop
3d: 90 nop
3e: 90 nop
3f: 90 nop
---
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 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.
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