[v5.15] Internal error in bpf_obj_get_info_by_fd

1 view
Skip to first unread message

syzbot

unread,
Aug 8, 2025, 11:59:39 AMAug 8
to syzkaller...@googlegroups.com
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=167355bc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=af96026e63d31cf9069e
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+af9602...@syzkaller.appspotmail.com

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4587 Comm: syz.3.194 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 : bpf_prog_get_info_by_fd kernel/bpf/syscall.c:3793 [inline]
pc : bpf_obj_get_info_by_fd+0x1cc4/0x30c0 kernel/bpf/syscall.c:4027
lr : bpf_prog_get_info_by_fd kernel/bpf/syscall.c:3793 [inline]
lr : bpf_obj_get_info_by_fd+0x1ca4/0x30c0 kernel/bpf/syscall.c:4027
sp : ffff800020127900
x29: ffff800020127bc0 x28: ffff700004024f34 x27: 0000000000000001
x26: 0000000000000000 x25: 0000000000000000 x24: 00000000fffffff2
x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000
x20: ffff80001fe9dc08 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000002 x16: ffff800008524f0c x15: 0000000000000001
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000002 x9 : 0000ffffffffffff
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
bpf_prog_get_info_by_fd kernel/bpf/syscall.c:3793 [inline]
bpf_obj_get_info_by_fd+0x1cc4/0x30c0 kernel/bpf/syscall.c:4027
__sys_bpf+0x39c/0x5f0 kernel/bpf/syscall.c:4690
__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 2a1603f8 2a1603e0 f8000914 (2a1803e1)
---[ end trace 0e82e9eecf4b0f1e ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1603f8 mov w24, w22
8: 2a1603e0 mov w0, w22
c: f8000914 sttr x20, [x8]
* 10: 2a1803e1 mov w1, w24 <-- 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

syzbot

unread,
5:52 AM (18 hours ago) 5:52 AM
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages