[syzbot] [net?] WARNING in __skb_flow_dissect (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dfdf77465620 net: airoha: Fix typo in airoha_ppe_setup_tc_..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=159d4052580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a94030c847137a18
dashboard link: https://syzkaller.appspot.com/bug?extid=c46409299c70a221415e
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f2960b575f2/disk-dfdf7746.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b48823d17c0/vmlinux-dfdf7746.xz
kernel image: https://storage.googleapis.com/syzbot-assets/852fefdd1d14/bzImage-dfdf7746.xz

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

------------[ cut here ]------------
WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0xb57/0x68b0 net/core/flow_dissector.c:1131, CPU#1: syz.2.1418/11053
Modules linked in:
CPU: 1 UID: 0 PID: 11053 Comm: syz.2.1418 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__skb_flow_dissect+0xb57/0x68b0 net/core/flow_dissector.c:1131
Code: 55 00 00 80 3d 94 c5 36 06 01 0f 85 b3 55 00 00 e8 be 8d 8b f8 e9 83 f9 ff ff e8 b4 8d 8b f8 e9 b0 03 00 00 e8 aa 8d 8b f8 90 <0f> 0b 90 e9 16 ff ff ff e8 9c 8d 8b f8 c6 05 5d c5 36 06 01 48 c7
RSP: 0000:ffffc900033a7100 EFLAGS: 00010287
RAX: ffffffff8935c70e RBX: 0000000000000001 RCX: 0000000000080000
RDX: ffffc9000d75c000 RSI: 0000000000000539 RDI: 000000000000053a
RBP: ffffc900033a7718 R08: ffffffff893562c8 R09: ffffffff8df41aa0
R10: ffffc900033a77a0 R11: fffff52000674efe R12: dffffc0000000000
R13: ffffffff893562c8 R14: 0000000000000000 R15: ffffffff8f825fd0
FS: 00007fea4dbe96c0(0000) GS:ffff888125f1f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c38c723 CR3: 00000000294c6000 CR4: 00000000003526f0
Call Trace:
<TASK>
bond_flow_dissect drivers/net/bonding/bond_main.c:4093 [inline]
__bond_xmit_hash+0x2d7/0xba0 drivers/net/bonding/bond_main.c:4157
bond_xmit_hash_xdp drivers/net/bonding/bond_main.c:4208 [inline]
bond_xdp_xmit_3ad_xor_slave_get drivers/net/bonding/bond_main.c:5139 [inline]
bond_xdp_get_xmit_slave+0x1fd/0x710 drivers/net/bonding/bond_main.c:5515
xdp_master_redirect+0x13f/0x2c0 net/core/filter.c:4388
bpf_prog_run_xdp include/net/xdp.h:700 [inline]
bpf_test_run+0x6b2/0x7d0 net/bpf/test_run.c:421
bpf_prog_test_run_xdp+0x795/0x10e0 net/bpf/test_run.c:1390
bpf_prog_test_run+0x2c7/0x340 kernel/bpf/syscall.c:4703
__sys_bpf+0x562/0x860 kernel/bpf/syscall.c:6182
__do_sys_bpf kernel/bpf/syscall.c:6274 [inline]
__se_sys_bpf kernel/bpf/syscall.c:6272 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:6272
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fea4cd8f749
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:00007fea4dbe9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fea4cfe5fa0 RCX: 00007fea4cd8f749
RDX: 0000000000000059 RSI: 0000200000000600 RDI: 000000000000000a
RBP: 00007fea4ce13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fea4cfe6038 R14: 00007fea4cfe5fa0 R15: 00007ffdb8efbed8
</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