[Android 5.4] kernel BUG in ip_do_fragment

4 views
Skip to first unread message

syzbot

unread,
Jun 8, 2023, 2:48:46 PM6/8/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 10e0626a3202 Merge "Merge tag 'android12-5.4.242_r00' into..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=167596fd280000
kernel config: https://syzkaller.appspot.com/x/.config?x=98c345379e95bc57
dashboard link: https://syzkaller.appspot.com/bug?extid=3358456fcd7b407fbc44
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175ceb95280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d5a51b280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/05e8a3da4c35/disk-10e0626a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/89055694184e/vmlinux-10e0626a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c7b418ae6a46/bzImage-10e0626a.xz

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

------------[ cut here ]------------
kernel BUG at net/core/dev.c:2871!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 359 Comm: syz-executor176 Not tainted 5.4.242-syzkaller-00065-g10e0626a3202 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:skb_checksum_help+0x873/0x880 net/core/dev.c:2871
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c d0 fc ff ff 48 89 df e8 8e cf 16 fe e9 c3 fc ff ff e8 64 15 e7 fd 0f 0b e8 5d 15 e7 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:ffff8881dbea6ea8 EFLAGS: 00010293
RAX: ffffffff837d1483 RBX: 0000000000000519 RCX: ffff8881dc0dcec0
RDX: 0000000000000000 RSI: 0000000000000519 RDI: 0000000000000621
RBP: 0000000000000621 R08: ffffffff837d0eff R09: ffffed103b7d4dc6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881f0b92e30
R13: 000000000000061f R14: ffff8881f0b92dc0 R15: 1ffff1103e1725c6
FS: 0000555555f94300(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001000 CR3: 00000001dbcc0000 CR4: 00000000003406b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ip_do_fragment+0x15e/0x2200 net/ipv4/ip_output.c:789
ip_finish_output_gso net/ipv4/ip_output.c:288 [inline]
__ip_finish_output+0x49c/0x710 net/ipv4/ip_output.c:311
NF_HOOK_COND include/linux/netfilter.h:297 [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+0x1a4e/0x2320 net/ipv4/ip_tunnel.c:817
__gre_xmit net/ipv4/ip_gre.c:442 [inline]
ipgre_xmit+0x7b3/0xac0 net/ipv4/ip_gre.c:634
__netdev_start_xmit include/linux/netdevice.h:4521 [inline]
netdev_start_xmit include/linux/netdevice.h:4535 [inline]
xmit_one net/core/dev.c:3211 [inline]
dev_hard_start_xmit+0x1b7/0x6b0 net/core/dev.c:3227
__dev_queue_xmit+0x14da/0x27e0 net/core/dev.c:3792
packet_snd net/packet/af_packet.c:3004 [inline]
packet_sendmsg+0x472e/0x60e0 net/packet/af_packet.c:3033
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
____sys_sendmsg+0x5ac/0x8f0 net/socket.c:2287
___sys_sendmsg net/socket.c:2341 [inline]
__sys_sendmsg+0x28b/0x380 net/socket.c:2387
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace 61bcb71e269dba38 ]---
RIP: 0010:skb_checksum_help+0x873/0x880 net/core/dev.c:2871
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c d0 fc ff ff 48 89 df e8 8e cf 16 fe e9 c3 fc ff ff e8 64 15 e7 fd 0f 0b e8 5d 15 e7 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:ffff8881dbea6ea8 EFLAGS: 00010293
RAX: ffffffff837d1483 RBX: 0000000000000519 RCX: ffff8881dc0dcec0
RDX: 0000000000000000 RSI: 0000000000000519 RDI: 0000000000000621
RBP: 0000000000000621 R08: ffffffff837d0eff R09: ffffed103b7d4dc6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881f0b92e30
R13: 000000000000061f R14: ffff8881f0b92dc0 R15: 1ffff1103e1725c6
FS: 0000555555f94300(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001000 CR3: 00000001dbcc0000 CR4: 00000000003406b0
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages