[Android 5.15] BUG: unable to handle kernel NULL pointer dereference in dev_queue_xmit_nit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 05ef4ccb5774 Revert "ipvlan: properly track tx_errors"
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=118e278ee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=efa97e9d20fc8142
dashboard link: https://syzkaller.appspot.com/bug?extid=f12ebc85232014b522b7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131ec6e1e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164ad5c1e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eb0b8726b8c3/disk-05ef4ccb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5021fc9cb78f/vmlinux-05ef4ccb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/279326f5d49b/bzImage-05ef4ccb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f12ebc...@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 0
P4D 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 287 Comm: sshd Not tainted 5.15.139-syzkaller-00529-g05ef4ccb5774 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0000:ffffc900009d76c0 EFLAGS: 00010246
RAX: 1ffff11023e1d251 RBX: 0000000000000000 RCX: ffff88811df84000
RDX: ffff88810a164780 RSI: ffff88811df84000 RDI: ffff88811f1d6c80
RBP: ffffc900009d7760 R08: ffffffff83e41457 R09: ffffed10214ea755
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88810a164780 R14: ffff88811f1d6d54 R15: ffff88810a164780
FS: 00007fc63e54c800(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011db6b000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dev_queue_xmit_nit+0x9a4/0xa40 net/core/dev.c:2349
xmit_one net/core/dev.c:3616 [inline]
dev_hard_start_xmit+0x149/0x620 net/core/dev.c:3637
__dev_queue_xmit+0x18b4/0x2e70 net/core/dev.c:4252
dev_queue_xmit+0x17/0x20 net/core/dev.c:4285
tipc_l2_send_msg+0x296/0x320 net/tipc/bearer.c:514
tipc_bearer_xmit_skb+0x2b1/0x3b0 net/tipc/bearer.c:560
tipc_disc_timeout+0x6fa/0x8b0 net/tipc/discover.c:338
call_timer_fn+0x3b/0x2d0 kernel/time/timer.c:1427
expire_timers kernel/time/timer.c:1472 [inline]
__run_timers+0x72a/0xa10 kernel/time/timer.c:1743
run_timer_softirq+0x69/0xf0 kernel/time/timer.c:1756
__do_softirq+0x26d/0x5bf kernel/softirq.c:565
invoke_softirq kernel/softirq.c:425 [inline]
__irq_exit_rcu+0x50/0xf0 kernel/softirq.c:648
irq_exit_rcu+0x9/0x10 kernel/softirq.c:660
common_interrupt+0x59/0xd0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x27/0x40 arch/x86/include/asm/idtentry.h:629
RIP: 0033:0x7fc63e624773
Code: 00 f3 a5 48 8d 74 24 88 48 b9 ff ff ff 7f fe ff ff ff 48 21 c8 48 89 44 24 88 41 ba 08 00 00 00 44 89 c7 b8 0e 00 00 00 0f 05 <45> 31 c0 3d 00 f0 ff ff 76 06 41 89 c0 41 f7 d8 44 89 c0 5a c3 41
RSP: 002b:00007ffd7d7629f0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fc63e624773
RDX: 00007ffd7d762ad8 RSI: 00007ffd7d762a58 RDI: 0000000000000000
RBP: 00005615541ef5e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 000056155323eaa4
R13: 0000000000000016 R14: 000056155323f3e8 R15: 00007ffd7d762a58
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace df2f22ee8c63e4d6 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0000:ffffc900009d76c0 EFLAGS: 00010246
RAX: 1ffff11023e1d251 RBX: 0000000000000000 RCX: ffff88811df84000
RDX: ffff88810a164780 RSI: ffff88811df84000 RDI: ffff88811f1d6c80
RBP: ffffc900009d7760 R08: ffffffff83e41457 R09: ffffed10214ea755
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88810a164780 R14: ffff88811f1d6d54 R15: ffff88810a164780
FS: 00007fc63e54c800(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011db6b000 CR4: 00000000003506b0
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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.
No recent activity, existing reproducers are no longer triggering the issue.