[v6.1] kernel BUG in pskb_expand_head

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=130322ed280000
kernel config: https://syzkaller.appspot.com/x/.config?x=11263f470b7a4c92
dashboard link: https://syzkaller.appspot.com/bug?extid=8106a9f80d9818d5ead8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b17a7cd87498/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc8291ae723a/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/04943541fc25/Image-d2869ace.gz.xz

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

------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:1833!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 13553 Comm: syz-executor.5 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : pskb_expand_head+0x105c/0x10b4 net/core/skbuff.c:1833
lr : pskb_expand_head+0x105c/0x10b4 net/core/skbuff.c:1833
sp : ffff80001f0273e0
x29: ffff80001f027440 x28: 00000000000002c0 x27: dfff800000000000
x26: 0000000000000000 x25: 0000000000000a20 x24: ffff8000103b5d98
x23: ffff0000cf0630cc x22: 0000000000000000 x21: 0000000000000002
x20: ffff0000cf0630cc x19: ffff0000cf063000 x18: 1fffe000368b9f76
x17: ffff8000155bd000 x16: ffff8000084fa384 x15: ffff0001b45cfbbc
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000040000
x11: 0000000000003ab0 x10: ffff80001dc99000 x9 : ffff80001039ba60
x8 : 0000000000003ab1 x7 : ffff8000105802d8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80001039aa90
x2 : 0000000000000000 x1 : 0000000000000002 x0 : 0000000000000001
Call trace:
pskb_expand_head+0x105c/0x10b4 net/core/skbuff.c:1833
skb_ensure_writable+0x244/0x388 net/core/skbuff.c:5760
__bpf_try_make_writable net/core/filter.c:1658 [inline]
sk_skb_try_make_writable net/core/filter.c:1870 [inline]
____sk_skb_pull_data net/core/filter.c:1884 [inline]
sk_skb_pull_data+0x7c/0xc8 net/core/filter.c:1873
bpf_prog_53daab6e9cefb4fc+0x50/0x80
bpf_dispatcher_nop_func include/linux/bpf.h:975 [inline]
__bpf_prog_run include/linux/filter.h:600 [inline]
bpf_prog_run include/linux/filter.h:607 [inline]
bpf_prog_run_pin_on_cpu+0x74/0x1e4 include/linux/filter.h:624
sk_psock_verdict_recv+0x27c/0x530 net/core/skmsg.c:1198
tcp_read_skb+0x384/0x5f8 net/ipv4/tcp.c:1774
sk_psock_verdict_data_ready+0x98/0xc4 net/core/skmsg.c:1215
tcp_data_ready+0x22c/0x450 net/ipv4/tcp_input.c:5005
tcp_rcv_established+0x12a4/0x1fe0 net/ipv4/tcp_input.c:5972
tcp_v4_do_rcv+0x390/0xb08 net/ipv4/tcp_ipv4.c:1671
sk_backlog_rcv include/net/sock.h:1109 [inline]
__release_sock+0x1a8/0x408 net/core/sock.c:2909
release_sock+0x68/0x1cc net/core/sock.c:3473
tcp_sendmsg+0x4c/0x64 net/ipv4/tcp.c:1487
inet_sendmsg+0x15c/0x290 net/ipv4/af_inet.c:828
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
__sys_sendto+0x3b4/0x504 net/socket.c:2117
__do_sys_sendto net/socket.c:2129 [inline]
__se_sys_sendto net/socket.c:2125 [inline]
__arm64_sys_sendto+0xd8/0xf8 net/socket.c:2125
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: d4210000 96057a4c d4210000 96057a4a (d4210000)
---[ end trace 0000000000000000 ]---


---
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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.