[v5.15] BUG: unable to handle kernel NULL pointer dereference in bq_xmit_all (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 74cdd62cb470 Linux 5.15.169
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13478540580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a532e68091e668cf
dashboard link: https://syzkaller.appspot.com/bug?extid=c5aa8700c2360f79e13a
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/9cd5ba5c8eb5/disk-74cdd62c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51345e3be25c/vmlinux-74cdd62c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9670d8303340/Image-74cdd62c.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5aa87...@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=0000000121765000
[0000000000000000] pgd=0800000107d2b003, p4d=0800000107d2b003, pud=080000011661e003, pmd=0000000000000000
Internal error: Oops: 0000000086000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6463 Comm: syz.4.493 Not tainted 5.15.169-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : bond_xdp_xmit+0x310/0x4f4 drivers/net/bonding/bond_main.c:5227
sp : ffff800020df7360
x29: ffff800020df74a0 x28: 1ffff000041bee8a x27: 1ffff000041bee86
x26: dfff800000000000 x25: ffff0000ceff4000 x24: ffff800020df7420
x23: ffff800020df7400 x22: ffff800012c801f8 x21: fffffbffeff9bf60
x20: ffff0000d8340140 x19: 0000000000000000 x18: 0000000000000200
x17: 0000000000000002 x16: ffff8000082eada8 x15: 0000000000000001
x14: ffff0000d5c31b40 x13: 0000000000ff0100 x12: 0000000000040000
x11: 0000000000000543 x10: ffff80002191e000 x9 : 0000000000000544
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000001
x2 : ffff800020df7400 x1 : 0000000000000001 x0 : ffff0000ceff4000
Call trace:
0x0
bq_xmit_all+0xcf4/0x111c kernel/bpf/devmap.c:388
__dev_flush+0xc8/0x1a0 kernel/bpf/devmap.c:418
xdp_do_flush+0x14/0x28 net/core/filter.c:3952
tun_build_skb drivers/net/tun.c:1703 [inline]
tun_get_user+0x27d8/0x3774 drivers/net/tun.c:1797
tun_chr_write_iter+0xfc/0x20c drivers/net/tun.c:2019
call_write_iter include/linux/fs.h:2174 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x884/0xb44 fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: bad PC value
---[ end trace dbfbe1a061bc3068 ]---


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