[Android 5.4] kernel BUG in validate_xmit_skb (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d0d34dcb02cc FROMLIST: binder: check offset alignment in b..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15ab2fe3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=60c0e8be982a03fd
dashboard link: https://syzkaller.appspot.com/bug?extid=7a364a716e54541201ed
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=10c0d339180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11337c75180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/de032a90cf4e/disk-d0d34dcb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f2bae6132625/vmlinux-d0d34dcb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c3043eb62d8/bzImage-d0d34dcb.xz

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

------------[ cut here ]------------
kernel BUG at net/core/dev.c:2873!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 356 Comm: syz-executor306 Not tainted 5.4.268-syzkaller-00012-gd0d34dcb02cc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:skb_checksum_help+0x873/0x880 net/core/dev.c:2873
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c d0 fc ff ff 48 89 df e8 2e 2b 16 fe e9 c3 fc ff ff e8 44 57 e6 fd 0f 0b e8 3d 57 e6 fd <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 53
RSP: 0018:ffff8881db846ca8 EFLAGS: 00010293
RAX: ffffffff837defe3 RBX: 0000000000002997 RCX: ffff8881de7a3f00
RDX: 0000000000000000 RSI: 0000000000002997 RDI: 0000000000003536
RBP: 0000000000003536 R08: ffffffff837dea5f R09: ffffed103b708d86
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881f3aee570
R13: 0000000000003534 R14: ffff8881f3aee500 R15: 1ffff1103e75dcae
FS: 000055555640d380(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000d000 CR3: 00000001db80b000 CR4: 00000000003406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
skb_csum_hwoffload_help net/core/dev.c:3271 [inline]
validate_xmit_skb+0x654/0xc50 net/core/dev.c:3314
__dev_queue_xmit+0xf7d/0x27e0 net/core/dev.c:3794
neigh_hh_output include/net/neighbour.h:502 [inline]
neigh_output include/net/neighbour.h:516 [inline]
ip_finish_output2+0xb4f/0xfc0 net/ipv4/ip_output.c:236
NF_HOOK_COND include/linux/netfilter.h:292 [inline]
ip_output+0x19b/0x3a0 net/ipv4/ip_output.c:440
iptunnel_xmit+0x476/0x850 net/ipv4/ip_tunnel_core.c:78
ip_tunnel_xmit+0x1aa7/0x26a0 net/ipv4/ip_tunnel.c:817
__gre_xmit net/ipv4/ip_gre.c:442 [inline]
ipgre_xmit+0x81a/0xbf0 net/ipv4/ip_gre.c:637
__netdev_start_xmit include/linux/netdevice.h:4538 [inline]
netdev_start_xmit include/linux/netdevice.h:4552 [inline]
xmit_one net/core/dev.c:3221 [inline]
dev_hard_start_xmit+0x1b7/0x6b0 net/core/dev.c:3237
__dev_queue_xmit+0x14da/0x27e0 net/core/dev.c:3802
packet_snd net/packet/af_packet.c:3009 [inline]
packet_sendmsg+0x4747/0x6100 net/packet/af_packet.c:3038
sock_sendmsg_nosec net/socket.c:638 [inline]
__sock_sendmsg net/socket.c:650 [inline]
____sys_sendmsg+0x5ac/0x8f0 net/socket.c:2306
___sys_sendmsg net/socket.c:2360 [inline]
__sys_sendmsg+0x28b/0x380 net/socket.c:2406
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace df8c96075c43db1e ]---
RIP: 0010:skb_checksum_help+0x873/0x880 net/core/dev.c:2873
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c d0 fc ff ff 48 89 df e8 2e 2b 16 fe e9 c3 fc ff ff e8 44 57 e6 fd 0f 0b e8 3d 57 e6 fd <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55 41 54 53
RSP: 0018:ffff8881db846ca8 EFLAGS: 00010293
RAX: ffffffff837defe3 RBX: 0000000000002997 RCX: ffff8881de7a3f00
RDX: 0000000000000000 RSI: 0000000000002997 RDI: 0000000000003536
RBP: 0000000000003536 R08: ffffffff837dea5f R09: ffffed103b708d86
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881f3aee570
R13: 0000000000003534 R14: ffff8881f3aee500 R15: 1ffff1103e75dcae
FS: 000055555640d380(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000d000 CR3: 00000001db80b000 CR4: 00000000003406a0
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