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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c16c81c81336 Linux 5.15.178
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11d7a654580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d302c69e93fb6774
dashboard link: https://syzkaller.appspot.com/bug?extid=de2d44312a2707cc57e7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/267e46ee7273/disk-c16c81c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/944e289206cf/vmlinux-c16c81c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f8cadf62458e/bzImage-c16c81c8.xz

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

BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 581cc067 P4D 581cc067 PUD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 7993 Comm: syz.1.1024 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90002f9f4f8 EFLAGS: 00010246
RAX: 1ffffffff175b13b RBX: ffffffff8bad89d8 RCX: 0000000000000001
RDX: ffffc90002f9f5a0 RSI: 0000000000000001 RDI: ffff8880632f8000
RBP: ffffc90002f9f670 R08: ffffffff857370b1 R09: ffffed100c65f008
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880632f8000
R13: ffff8880265d0140 R14: ffffe8ffffc4c140 R15: dffffc0000000000
FS: 00007f675980a6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000564bb000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
bond_xdp_xmit+0x380/0x570 drivers/net/bonding/bond_main.c:5228
bq_xmit_all+0xd1d/0x1100 kernel/bpf/devmap.c:391
__dev_flush+0xc9/0x1c0 kernel/bpf/devmap.c:421
xdp_do_flush+0xa/0x20 net/core/filter.c:3977
tun_build_skb drivers/net/tun.c:1703 [inline]
tun_get_user+0x2f4a/0x40f0 drivers/net/tun.c:1797
tun_chr_write_iter+0x10c/0x1e0 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+0xacd/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f675b99fc1f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 f9 92 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 4c 93 02 00 48
RSP: 002b:00007f675980a000 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f675bbb9fa0 RCX: 00007f675b99fc1f
RDX: 0000000000000042 RSI: 0000400000000a40 RDI: 00000000000000c8
RBP: 00007f675ba222a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000042 R11: 0000000000000293 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f675bbb9fa0 R15: 00007ffff9519d78
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace c11335995a4f94bd ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90002f9f4f8 EFLAGS: 00010246
RAX: 1ffffffff175b13b RBX: ffffffff8bad89d8 RCX: 0000000000000001
RDX: ffffc90002f9f5a0 RSI: 0000000000000001 RDI: ffff8880632f8000
RBP: ffffc90002f9f670 R08: ffffffff857370b1 R09: ffffed100c65f008
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880632f8000
R13: ffff8880265d0140 R14: ffffe8ffffc4c140 R15: dffffc0000000000
FS: 00007f675980a6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000564bb000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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