possible deadlock in sock_close

Status: upstream: reported on 2026/10/09 00:02
Reported-by: syzbot+175ab246871db9ff9256@syzkaller.appspotmail.com
First crash: 9d18h, last: 4h50m
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in sock_close 4 1 9d08h 9d08h 0/3 upstream: reported on 2026/10/09 10:25

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.850/6940 is trying to acquire lock:
ffff888056640210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
ffff888056640210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
ffff888056640210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x82/0x210 net/socket.c:1400

but task is already holding lock:
ffff888028910d40 (&wdev->mtx){+.+.}-{3:3}, at: wdev_lock net/wireless/core.h:231 [inline]
ffff888028910d40 (&wdev->mtx){+.+.}-{3:3}, at: cfg80211_wext_siwgenie+0xd4/0x3f0 net/wireless/wext-sme.c:340

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&wdev->mtx){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       wdev_lock net/wireless/core.h:231 [inline]
       cfg80211_wext_siwgenie+0xd4/0x3f0 net/wireless/wext-sme.c:340
       ioctl_standard_iw_point+0x823/0xd50 net/wireless/wext-core.c:848
       ioctl_standard_call+0xaa/0x250 net/wireless/wext-core.c:1033
       wireless_process_ioctl net/wireless/wext-core.c:964 [inline]
       wext_ioctl_dispatch+0x3da/0x470 net/wireless/wext-core.c:997
       wext_handle_ioctl+0x114/0x1d0 net/wireless/wext-core.c:1058
       sock_ioctl+0x143/0x700 net/socket.c:1253
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (rtnl_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       ip_mc_drop_socket+0x7c/0x270 net/ipv4/igmp.c:2706
       inet_release+0x47/0x180 net/ipv4/af_inet.c:417
       __sock_release net/socket.c:654 [inline]
       sock_close+0xbf/0x210 net/socket.c:1400
       __fput+0x20a/0x8b0 fs/file_table.c:320
       task_work_run+0x1d0/0x260 kernel/task_work.c:203
       get_signal+0x118d/0x1340 kernel/signal.c:2661
       arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871
       exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:177
       exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:213
       __syscall_exit_to_user_mode_work kernel/entry/common.c:295 [inline]
       syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:306
       do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3162 [inline]
       check_prevs_add kernel/locking/lockdep.c:3281 [inline]
       validate_chain kernel/locking/lockdep.c:3897 [inline]
       __lock_acquire+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
       lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:764 [inline]
       __sock_release net/socket.c:653 [inline]
       sock_close+0x82/0x210 net/socket.c:1400
       __fput+0x20a/0x8b0 fs/file_table.c:320
       task_work_run+0x1d0/0x260 kernel/task_work.c:203
       get_signal+0x118d/0x1340 kernel/signal.c:2661
       arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871
       exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:177
       exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:213
       __syscall_exit_to_user_mode_work kernel/entry/common.c:295 [inline]
       syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:306
       do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &sb->s_type->i_mutex_key#11 --> rtnl_mutex --> &wdev->mtx

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&wdev->mtx);
                               lock(rtnl_mutex);
                               lock(&wdev->mtx);
  lock(&sb->s_type->i_mutex_key#11);

 *** DEADLOCK ***

1 lock held by syz.2.850/6940:
 #0: ffff888028910d40 (&wdev->mtx){+.+.}-{3:3}, at: wdev_lock net/wireless/core.h:231 [inline]
 #0: ffff888028910d40 (&wdev->mtx){+.+.}-{3:3}, at: cfg80211_wext_siwgenie+0xd4/0x3f0 net/wireless/wext-sme.c:340

stack backtrace:
CPU: 0 PID: 6940 Comm: syz.2.850 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x2f8/0x400 kernel/locking/lockdep.c:2215
 check_prev_add kernel/locking/lockdep.c:3162 [inline]
 check_prevs_add kernel/locking/lockdep.c:3281 [inline]
 validate_chain kernel/locking/lockdep.c:3897 [inline]
 __lock_acquire+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
 lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
 down_write+0x36/0x60 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:764 [inline]
 __sock_release net/socket.c:653 [inline]
 sock_close+0x82/0x210 net/socket.c:1400
 __fput+0x20a/0x8b0 fs/file_table.c:320
 task_work_run+0x1d0/0x260 kernel/task_work.c:203
 get_signal+0x118d/0x1340 kernel/signal.c:2661
 arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871
 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:177
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:213
 __syscall_exit_to_user_mode_work kernel/entry/common.c:295 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:306
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f77ec59e559
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f77ed54d028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffea RBX: 00007f77ec825fa0 RCX: 00007f77ec59e559
RDX: 0000200000000040 RSI: 0000000000008b30 RDI: 0000000000000004
RBP: 00007f77ec635ab8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f77ec826038 R14: 00007f77ec825fa0 R15: 00007fff58b8cee8
 </TASK>

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/17 10:20 linux-6.1.y 79807e970724 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in sock_close
2026/10/10 04:50 linux-6.1.y a500ba24937a 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in sock_close
2026/10/09 13:48 linux-6.1.y a500ba24937a b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in sock_close
2026/10/18 14:03 linux-6.1.y 79807e970724 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/17 17:00 linux-6.1.y 79807e970724 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/13 13:08 linux-6.1.y a500ba24937a 5a1eeac4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/12 16:43 linux-6.1.y a500ba24937a 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/10 07:24 linux-6.1.y a500ba24937a 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/10 01:24 linux-6.1.y a500ba24937a 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/09 00:02 linux-6.1.y a500ba24937a b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
2026/10/09 00:01 linux-6.1.y a500ba24937a b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in sock_close
* Struck through repros no longer work on HEAD.