[v5.15] WARNING in resolve_pseudo_ldimm64

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17770d0c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=db74c56dea20051
dashboard link: https://syzkaller.appspot.com/bug?extid=7d29f5065393d0d93007
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6f961932e2f9/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/324c9e53c038/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6148f0d6768f/bzImage-1c700860.xz

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

------------[ cut here ]------------
trace type BPF program uses run-time allocation
WARNING: CPU: 0 PID: 5035 at kernel/bpf/verifier.c:11729 check_map_prog_compatibility+0x6cf/0x870 kernel/bpf/verifier.c:11729
Modules linked in:
CPU: 1 PID: 5035 Comm: syz.6.85 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Code: ff e8 45 df ef ff 48 c7 c6 60 23 11 8a e9 0d fd ff ff e8 34 df ef ff c6 05 1d 2c cd 0b 01 48 c7 c7 c0 1f 11 8a e8 f1 c4 0e 08 <0f> 0b e9 9f fb ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c a5 f9
RSP: 0018:ffffc900035bf450 EFLAGS: 00010246
RAX: b86a80dcdd71c300 RBX: 0000000000000001 RCX: 0000000000080000
RDX: ffffc9001a84f000 RSI: 00000000000333df RDI: 00000000000333e0
RBP: ffff88805e3c4000 R08: dffffc0000000000 R09: ffffed10172067a8
R10: ffffed10172067a8 R11: 1ffff110172067a7 R12: ffffc90000d7e038
R13: 0000000000000011 R14: dffffc0000000000 R15: 1ffff920001afc07
FS: 00007fd705a9b6c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557334ab1660 CR3: 000000007de21000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
resolve_pseudo_ldimm64+0x685/0x11d0 kernel/bpf/verifier.c:11898
bpf_check+0x30a4/0xf090 kernel/bpf/verifier.c:14104
bpf_prog_load+0x1043/0x1550 kernel/bpf/syscall.c:2348
__sys_bpf+0x4c2/0x670 kernel/bpf/syscall.c:4651
__do_sys_bpf kernel/bpf/syscall.c:4755 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4753 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4753
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fd707c33929
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:00007fd705a9b038 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fd707e5afa0 RCX: 00007fd707c33929
RDX: 0000000000000090 RSI: 00002000000000c0 RDI: 0000000000000005
RBP: 00007fd707cb5b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fd707e5afa0 R15: 00007ffe668c1d18
</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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.