[v6.1] BUG: unable to handle kernel NULL pointer dereference in bq_xmit_all

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1532abfc980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f084fbeeff2de042
dashboard link: https://syzkaller.appspot.com/bug?extid=8613615616552a1b83b8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9040ec940045/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dc70128611fd/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f05abc0b618b/Image-88690811.gz.xz

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

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mem abort info:
ESR = 0x0000000086000006
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=00000001140ae000
[0000000000000000] pgd=0800000127f7d003, p4d=0800000127f7d003, pud=08000001106de003, pmd=0000000000000000
Internal error: Oops: 0000000086000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 7777 Comm: syz-executor.4 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : bond_xdp_xmit+0x34c/0x588 drivers/net/bonding/bond_main.c:5546
sp : ffff800022146ea0
x29: ffff800022147000 x28: 1ffff00004428df2 x27: ffff0000db2cc000
x26: ffff0000c9765198 x25: 1ffff00004428df6 x24: ffff800022146f80
x23: ffff800022146f60 x22: dfff800000000000 x21: fffffbffeff9aa10
x20: ffff800014270d18 x19: 0000000000000000 x18: 1ffff00004428dec
x17: 0000000000000000 x16: ffff800008304340 x15: 0000000000000002
x14: 0000000000000001 x13: ffff0000cd3c8000 x12: 0000000000040000
x11: 00000000000022d7 x10: ffff80001e3d9000 x9 : ffff80000ca71a70
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
x2 : ffff800022146f60 x1 : 0000000000000001 x0 : ffff0000db2cc000
Call trace:
0x0
bq_xmit_all+0xb48/0xffc kernel/bpf/devmap.c:389
bq_enqueue+0x288/0x30c kernel/bpf/devmap.c:454
dev_map_enqueue_multi+0xc80/0xdac kernel/bpf/devmap.c:653
__xdp_do_redirect_frame net/core/filter.c:4276 [inline]
xdp_do_redirect_frame+0x400/0x5a8 net/core/filter.c:4341
xdp_test_run_batch net/bpf/test_run.c:314 [inline]
bpf_test_run_xdp_live+0x9a4/0x18a0 net/bpf/test_run.c:362
bpf_prog_test_run_xdp+0x670/0xf60 net/bpf/test_run.c:1387
bpf_prog_test_run+0x2dc/0x364 kernel/bpf/syscall.c:3670
__sys_bpf+0x390/0x654 kernel/bpf/syscall.c:5023
__do_sys_bpf kernel/bpf/syscall.c:5109 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5107 [inline]
__arm64_sys_bpf+0x80/0x98 kernel/bpf/syscall.c:5107
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: bad PC value
---[ end trace 0000000000000000 ]---


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