syzbot


kernel BUG in set_ipsecrequest

Status: upstream: reported C repro on 2025/10/17 05:53
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+be97dd4da14ae88b6ba4@syzkaller.appspotmail.com
First crash: 20d, last: 9d00h
Cause bisection: introduced by (bisect log) :
commit 14ad6ed30a10afbe91b0749d6378285f4225d482
Author: Paolo Abeni <pabeni@redhat.com>
Date: Tue Feb 18 18:29:39 2025 +0000

  net: allow small head cache usage with large MAX_SKB_FRAGS values

Crash: kernel BUG in set_ipsecrequest (log)
Repro: C syz .config
  
Discussions (9)
Title Replies (including bot) Last reply
[PATCH] key: No support for family zero 2 (2) 2025/10/27 21:00
[PATCH] net: key: Validate address family in set_ipsecrequest() 2 (3) 2025/10/27 20:59
[PATCH net] net: key: Fix potential integer overflow in set_ipsecrequest 2 (2) 2025/10/27 20:37
[PATCH] fix integer overflow in set_ipsecrequest 1 (1) 2025/10/21 03:00
[syzbot] [net?] kernel BUG in set_ipsecrequest 1 (8) 2025/10/20 11:19
[PATCH] Fix integer overflow in set_ipsecrequest() 2 (4) 2025/10/20 07:48
Re: [syzbot] [net?] kernel BUG in set_ipsecrequest 1 (1) 2025/10/20 06:03
Re: [syzbot] [net?] kernel BUG in set_ipsecrequest 1 (1) 2025/10/20 06:00
[PATCH] net: key: Validate address family in set_ipsecrequest() 1 (1) 2025/10/19 18:14
Last patch testing requests (9)
Created Duration User Patch Repo Result
2025/10/20 11:19 54m clf700383@gmail.com patch bpf-next OK log
2025/10/20 07:54 1m clf700383@gmail.com patch bpf-next error
2025/10/20 07:47 0m clf700383@gmail.com patch bpf-next error
2025/10/20 07:30 3m clf700383@gmail.com patch bpf-next error
2025/10/20 02:57 17m ssrane_b23@ee.vjti.ac.in bpf-next report log
2025/10/20 02:50 1m ssrane_b23@ee.vjti.ac.in patch bpf-next error
2025/10/19 18:29 0m ssranevjti@gmail.com patch upstream error
2025/10/19 18:26 0m ssranevjti@gmail.com patch upstream error
2025/10/19 18:22 8m ssranevjti@gmail.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master error

Sample crash report:
skbuff: skb_over_panic: text:ffffffff8a19dc03 len:392 put:16 head:ffff88807680ad80 data:ffff88807680ad80 tail:0x188 end:0x180 dev:<NULL>
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:212!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6048 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:212
Code: c7 20 ac 6c 8c 48 8b 74 24 08 48 8b 54 24 10 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 55 41 57 41 56 e8 de 93 f5 ff 48 83 c4 20 90 <0f> 0b cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900038b6b68 EFLAGS: 00010282
RAX: 0000000000000088 RBX: dffffc0000000000 RCX: e3bc651cd751a000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000180 R08: ffffc900038b6867 R09: 1ffff92000716d0c
R10: dffffc0000000000 R11: fffff52000716d0d R12: ffff888076ae8290
R13: ffff88807680ad80 R14: ffff88807680ad80 R15: 0000000000000188
FS:  000055557c6b2500(0000) GS:ffff88812613e000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001f40 CR3: 00000000756c2000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 skb_over_panic net/core/skbuff.c:217 [inline]
 skb_put+0x159/0x210 net/core/skbuff.c:2583
 skb_put_zero include/linux/skbuff.h:2788 [inline]
 set_ipsecrequest+0x73/0x680 net/key/af_key.c:3532
 pfkey_send_migrate+0x11f2/0x1de0 net/key/af_key.c:3636
 km_migrate+0x155/0x260 net/xfrm/xfrm_state.c:2838
 xfrm_migrate+0x2020/0x2330 net/xfrm/xfrm_policy.c:4698
 xfrm_do_migrate+0x796/0x900 net/xfrm/xfrm_user.c:3144
 xfrm_user_rcv_msg+0x7a3/0xab0 net/xfrm/xfrm_user.c:3501
 netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552
 xfrm_netlink_rcv+0x79/0x90 net/xfrm/xfrm_user.c:3523
 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
 netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1346
 netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896
 sock_sendmsg_nosec net/socket.c:727 [inline]
 __sock_sendmsg+0x21c/0x270 net/socket.c:742
 ____sys_sendmsg+0x505/0x830 net/socket.c:2630
 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2684
 __sys_sendmsg net/socket.c:2716 [inline]
 __do_sys_sendmsg net/socket.c:2721 [inline]
 __se_sys_sendmsg net/socket.c:2719 [inline]
 __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2719
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fca9c18efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcc15540f8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fca9c3e5fa0 RCX: 00007fca9c18efc9
RDX: 0000000000000000 RSI: 0000200000000380 RDI: 0000000000000004
RBP: 00007fca9c211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fca9c3e5fa0 R14: 00007fca9c3e5fa0 R15: 0000000000000003
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:212
Code: c7 20 ac 6c 8c 48 8b 74 24 08 48 8b 54 24 10 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 55 41 57 41 56 e8 de 93 f5 ff 48 83 c4 20 90 <0f> 0b cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900038b6b68 EFLAGS: 00010282
RAX: 0000000000000088 RBX: dffffc0000000000 RCX: e3bc651cd751a000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000180 R08: ffffc900038b6867 R09: 1ffff92000716d0c
R10: dffffc0000000000 R11: fffff52000716d0d R12: ffff888076ae8290
R13: ffff88807680ad80 R14: ffff88807680ad80 R15: 0000000000000188
FS:  000055557c6b2500(0000) GS:ffff88812613e000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001f40 CR3: 00000000756c2000 CR4: 00000000003526f0

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/23 14:18 bpf 881a9c9cb785 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce kernel BUG in set_ipsecrequest
2025/10/17 01:09 bpf-next 48a97ffc6c82 19568248 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce kernel BUG in set_ipsecrequest
2025/10/17 00:20 bpf-next 48a97ffc6c82 19568248 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce kernel BUG in set_ipsecrequest
2025/10/16 22:30 bpf-next 48a97ffc6c82 19568248 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce kernel BUG in set_ipsecrequest
2025/10/17 01:42 linux-next 2433b8476165 19568248 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce kernel BUG in set_ipsecrequest
2025/10/28 12:34 net-next 5f30bc470672 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce kernel BUG in set_ipsecrequest
2025/10/16 21:39 bpf-next 48a97ffc6c82 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce kernel BUG in set_ipsecrequest
* Struck through repros no longer work on HEAD.