[v5.15] kernel BUG in eth_header

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 91786f140358 Linux 5.15.175
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12b4cadf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1fc30776feb70ea7
dashboard link: https://syzkaller.appspot.com/bug?extid=4faf436f5206a5e5ce7f
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/210b1e4b59b1/disk-91786f14.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1cf8391059a0/vmlinux-91786f14.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1d9077a44b1c/bzImage-91786f14.xz

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

skbuff: skb_under_panic: text:ffffffff88740834 len:74 put:14 head:ffff888060e1d800 data:ffff888060e1d7f2 tail:0x3c end:0xc0 dev:syz_tun
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:112!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 13138 Comm: syz.5.2541 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:skb_panic net/core/skbuff.c:112 [inline]
RIP: 0010:skb_under_panic+0x143/0x150 net/core/skbuff.c:122
Code: 04 9e 8b 48 c7 c6 93 da 55 8c 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 55 41 54 41 57 41 56 e8 e1 cd ed 01 48 83 c4 20 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc90003f7ea70 EFLAGS: 00010282
RAX: 0000000000000087 RBX: dffffc0000000000 RCX: d1a4c989a1983f00
RDX: ffffc900132d9000 RSI: 0000000000004c88 RDI: 0000000000004c89
RBP: ffff8880722c4000 R08: ffffffff8166aa6c R09: fffffbfff1c14c0e
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000000000c0
R13: ffff888060e1d800 R14: ffff888060e1d7f2 R15: 000000000000003c
FS: 00007f255acbb6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e01dff8 CR3: 00000000645bd000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
skb_push+0xdd/0x100 net/core/skbuff.c:2053
eth_header+0x34/0x1e0 net/ethernet/eth.c:82
dev_hard_header include/linux/netdevice.h:3288 [inline]
nf_send_reset6+0xd20/0x1250 net/ipv6/netfilter/nf_reject_ipv6.c:354
nft_reject_inet_eval+0x3b5/0x680 net/netfilter/nft_reject_inet.c:48
expr_call_ops_eval net/netfilter/nf_tables_core.c:198 [inline]
nft_do_chain+0x467/0x16b0 net/netfilter/nf_tables_core.c:238
nft_do_chain_inet+0x3f8/0x680 net/netfilter/nft_chain_filter.c:161
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_slow+0xae/0x1e0 net/netfilter/core.c:584
nf_hook include/linux/netfilter.h:257 [inline]
NF_HOOK include/linux/netfilter.h:300 [inline]
br_nf_pre_routing_ipv6+0x5fa/0x720 net/bridge/br_netfilter_ipv6.c:237
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_bridge_pre net/bridge/br_input.c:242 [inline]
br_handle_frame+0x8a8/0x10e0 net/bridge/br_input.c:384
__netif_receive_skb_core+0x13b9/0x3df0 net/core/dev.c:5387
__netif_receive_skb_one_core net/core/dev.c:5491 [inline]
__netif_receive_skb+0x11c/0x530 net/core/dev.c:5607
netif_receive_skb_internal net/core/dev.c:5693 [inline]
netif_receive_skb+0x1b4/0x760 net/core/dev.c:5752
tun_rx_batched+0x6bc/0x860
tun_get_user+0x2a1c/0x40f0 drivers/net/tun.c:1989
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:0x7f255ce497df
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:00007f255acbb000 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f255d03afa0 RCX: 00007f255ce497df
RDX: 000000000000004a RSI: 0000000020000000 RDI: 00000000000000c8
RBP: 00007f255cec6aa8 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000004a R11: 0000000000000293 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f255d03afa0 R15: 00007ffcdf585308
</TASK>
Modules linked in:
---[ end trace cb07572b19d45d67 ]---
RIP: 0010:skb_panic net/core/skbuff.c:112 [inline]
RIP: 0010:skb_under_panic+0x143/0x150 net/core/skbuff.c:122
Code: 04 9e 8b 48 c7 c6 93 da 55 8c 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 55 41 54 41 57 41 56 e8 e1 cd ed 01 48 83 c4 20 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 90 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc90003f7ea70 EFLAGS: 00010282
RAX: 0000000000000087 RBX: dffffc0000000000 RCX: d1a4c989a1983f00
RDX: ffffc900132d9000 RSI: 0000000000004c88 RDI: 0000000000004c89
RBP: ffff8880722c4000 R08: ffffffff8166aa6c R09: fffffbfff1c14c0e
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000000000c0
R13: ffff888060e1d800 R14: ffff888060e1d7f2 R15: 000000000000003c
FS: 00007f255acbb6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e01dff8 CR3: 00000000645bd000 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