syzbot


possible deadlock in ipv6_sock_mc_close (4)

Status: fixed on 2026/01/21 09:45
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+c59e6bb54e7620495725@syzkaller.appspotmail.com
Fix commit: b98f06f9a5d3 sctp: Fetch inet6_sk() after setting ->pinet6 in sctp_clone_sock().
First crash: 52d, last: 50d
Cause bisection: introduced by (bisect log) :
commit b7ddb55f31279f4e59acde3395fc03c3d94b6e5f
Author: Kuniyuki Iwashima <kuniyu@google.com>
Date: Thu Oct 23 23:16:56 2025 +0000

  sctp: Use sctp_clone_sock() in sctp_do_peeloff().

Crash: possible deadlock in ipv6_sock_mc_close (log)
Repro: C syz .config
  
Discussions (3)
Title Replies (including bot) Last reply
[PATCH v2 net 1/2] sctp: Fetch inet6_sk() after setting ->pinet6 in sctp_clone_sock(). 1 (1) 2025/12/10 08:11
[PATCH v1 net 1/2] sctp: Fetch inet6_sk() after setting ->pinet6 in sctp_clone_sock(). 1 (1) 2025/12/08 13:36
[syzbot] [net?] possible deadlock in ipv6_sock_mc_close (4) 0 (1) 2025/12/08 13:22
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ipv6_sock_mc_close (2) net 4 1 511d 509d 0/29 auto-obsoleted due to no activity on 2024/12/10 03:31
upstream possible deadlock in ipv6_sock_mc_close (3) net 4 1 388d 384d 0/29 auto-obsoleted due to no activity on 2025/04/12 07:57
upstream possible deadlock in ipv6_sock_mc_close net 4 C done unreliable 6 1753d 1791d 0/29 closed as invalid on 2023/08/03 10:00
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/12/08 10:25 39m kuniyu@google.com patch net-next OK log
2025/12/08 09:41 36m kuniyu@google.com patch net-next report log

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/5996 is trying to acquire lock:
ffff888031af4c60 (sk_lock-AF_INET6){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1700 [inline]
ffff888031af4c60 (sk_lock-AF_INET6){+.+.}-{0:0}, at: ipv6_sock_mc_close+0xd3/0x140 net/ipv6/mcast.c:348

but task is already holding lock:
ffff888031af4320 (sk_lock-AF_INET6){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1700 [inline]
ffff888031af4320 (sk_lock-AF_INET6){+.+.}-{0:0}, at: sctp_getsockopt+0x135/0xb60 net/sctp/socket.c:8131

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(sk_lock-AF_INET6);
  lock(sk_lock-AF_INET6);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by syz.0.17/5996:
 #0: ffff888031af4320 (sk_lock-AF_INET6){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1700 [inline]
 #0: ffff888031af4320 (sk_lock-AF_INET6){+.+.}-{0:0}, at: sctp_getsockopt+0x135/0xb60 net/sctp/socket.c:8131

stack backtrace:
CPU: 0 UID: 0 PID: 5996 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x2540/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868
 lock_sock_nested+0x48/0x100 net/core/sock.c:3780
 lock_sock include/net/sock.h:1700 [inline]
 ipv6_sock_mc_close+0xd3/0x140 net/ipv6/mcast.c:348
 inet6_release+0x47/0x70 net/ipv6/af_inet6.c:482
 __sock_release net/socket.c:653 [inline]
 sock_release+0x85/0x150 net/socket.c:681
 sctp_getsockopt_peeloff_common+0x56b/0x770 net/sctp/socket.c:5732
 sctp_getsockopt_peeloff_flags+0x13b/0x230 net/sctp/socket.c:5801
 sctp_getsockopt+0x3ab/0xb60 net/sctp/socket.c:8151
 do_sock_getsockopt+0x2b4/0x3d0 net/socket.c:2399
 __sys_getsockopt net/socket.c:2428 [inline]
 __do_sys_getsockopt net/socket.c:2435 [inline]
 __se_sys_getsockopt net/socket.c:2432 [inline]
 __x64_sys_getsockopt+0x1a5/0x250 net/socket.c:2432
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8f8c38f749
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:00007ffcfdade018 EFLAGS: 00000246 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00007f8f8c5e5fa0 RCX: 00007f8f8c38f749
RDX: 000000000000007a RSI: 0000000000000084 RDI: 0000000000000003
RBP: 00007f8f8c413f91 R08: 0000200000000040 R09: 0000000000000000
R10: 0000200000000340 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8f8c5e5fa0 R14: 00007f8f8c5e5fa0 R15: 0000000000000005
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/04 22:19 net-next 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/04 20:45 net-next 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/04 19:14 net-next 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/04 17:43 net-next 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/04 16:04 net-next 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/06 07:02 linux-next 6987d58a9cbc d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in ipv6_sock_mc_close
2025/12/04 14:34 net-next 8f7aa3d3c732 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ipv6_sock_mc_close
* Struck through repros no longer work on HEAD.