Hello,
syzbot found the following issue on:
HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10b0b2f0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link:
https://syzkaller.appspot.com/bug?extid=12f61f5e1a1ea72e33d1
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+12f61f...@syzkaller.appspotmail.com
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4166 Comm: syz.3.7 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : generic_map_lookup_batch+0x400/0xd50 kernel/bpf/syscall.c:1466
lr : generic_map_lookup_batch+0x3dc/0xd50 kernel/bpf/syscall.c:1466
sp : ffff80001fcd7a20
x29: ffff80001fcd7b50 x28: dfff800000000000 x27: 1ffff00003f9af5c
x26: 0000000000002318 x25: 0000000020000260 x24: 0000002000026000
x23: 00000000fffffff2 x22: fffffff800000107 x21: ffff80001fcd7c68
x20: ffff0000cd274c00 x19: 1ffff00003f9af8d x18: 0000000000000000
x17: 0000000000000002 x16: ffff800008518cdc x15: 0000000000000015
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000020000260 x9 : 0000ffffffffffff
x8 : 0000000020000260 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
generic_map_lookup_batch+0x400/0xd50 kernel/bpf/syscall.c:1466
bpf_map_do_batch+0x260/0x530 kernel/bpf/syscall.c:4233
__sys_bpf+0x368/0x5f0 kernel/bpf/syscall.c:-1
__do_sys_bpf kernel/bpf/syscall.c:4755 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4753 [inline]
__arm64_sys_bpf+0x80/0x98 kernel/bpf/syscall.c:4753
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1f03f7 2a1f03e0 b8000957 (2a1703e1)
---[ end trace 1fac5ee6e20a9c7d ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1f03f7 mov w23, wzr
8: 2a1f03e0 mov w0, wzr
c: b8000957 sttr w23, [x10]
* 10: 2a1703e1 mov w1, w23 <-- trapping instruction
---
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