syzbot


inconsistent lock state in valid_state (3)

Status: upstream: reported C repro on 2026/04/20 22:51
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+c8eb6060abf5a2a7b274@syzkaller.appspotmail.com
First crash: 6d17h, last: 2d11h
Bug presence (1)
Date Name Commit Repro Result
2026/04/22 upstream (ToT) 6596a02b2078 C [report] inconsistent lock state in __sk_receive_skb
Similar bugs (11)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 inconsistent lock state in valid_state (2) missing-backport 4 C done 208 557d 774d 0/3 auto-obsoleted due to no activity on 2024/12/26 10:49
linux-6.6 inconsistent lock state in valid_state origin:upstream 4 C 2 8d15h 8d21h 0/2 upstream: reported C repro on 2026/04/18 18:50
upstream inconsistent lock state in valid_state (6) kernfs comedi 4 2 190d 189d 0/29 auto-obsoleted due to no activity on 2026/01/26 19:03
upstream inconsistent lock state in valid_state kernel 4 1 1159d 1155d 0/29 auto-obsoleted due to no activity on 2023/06/23 05:39
upstream inconsistent lock state in valid_state (4) linux1394 ppp 4 C error 72 440d 616d 0/29 auto-obsoleted due to no activity on 2025/04/21 16:31
linux-5.15 inconsistent lock state in valid_state 4 2 1047d 1126d 0/3 auto-obsoleted due to no activity on 2023/09/22 20:18
linux-6.1 inconsistent lock state in valid_state (2) origin:upstream missing-backport 4 C done 338 6d13h 947d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (5) net 4 515 236d 240d 0/29 closed as invalid on 2025/09/16 17:45
upstream inconsistent lock state in valid_state (2) sound 4 C inconclusive 57405 686d 810d 25/29 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm 4 C error 376 633d 682d 27/29 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 4 1 1128d 1128d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
syz.0.25/4374 [HC0[0]:SC0[0]:HE1:SE1] takes:
ffff88807f0e4560 (slock-AF_PHONET/1){+.?.}-{2:2}, at: __sk_receive_skb+0x17b/0x980 net/core/sock.c:517
{IN-SOFTIRQ-W} state was registered at:
  lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
  _raw_spin_lock_nested+0x2e/0x40 kernel/locking/spinlock.c:368
  __sk_receive_skb+0x17b/0x980 net/core/sock.c:517
  sk_backlog_rcv include/net/sock.h:1080 [inline]
  __sk_receive_skb+0x42c/0x980 net/core/sock.c:526
  sk_receive_skb include/net/sock.h:2001 [inline]
  phonet_rcv+0x7e4/0xc70 net/phonet/af_phonet.c:405
  __netif_receive_skb_one_core net/core/dev.c:5551 [inline]
  __netif_receive_skb+0xcc/0x290 net/core/dev.c:5665
  process_backlog+0x370/0x790 net/core/dev.c:6542
  __napi_poll+0xc0/0x430 net/core/dev.c:7101
  napi_poll net/core/dev.c:7168 [inline]
  net_rx_action+0x4d4/0xa10 net/core/dev.c:7258
  handle_softirqs+0x339/0x830 kernel/softirq.c:576
  run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
  smpboot_thread_fn+0x4f6/0x970 kernel/smpboot.c:164
  kthread+0x436/0x520 kernel/kthread.c:334
  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
irq event stamp: 61
hardirqs last  enabled at (61): [<ffffffff81494d76>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (59): [<ffffffff81494d17>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last  enabled at (60): [<ffffffff87dbff48>] spin_unlock_bh include/linux/spinlock.h:409 [inline]
softirqs last  enabled at (60): [<ffffffff87dbff48>] __release_sock+0xa8/0x450 net/core/sock.c:2724
softirqs last disabled at (58): [<ffffffff87db2f5b>] spin_lock_bh include/linux/spinlock.h:369 [inline]
softirqs last disabled at (58): [<ffffffff87db2f5b>] release_sock+0x2b/0x1b0 net/core/sock.c:3272

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

       CPU0
       ----
  lock(slock-AF_PHONET/1);
  <Interrupt>
    lock(slock-AF_PHONET/1);

 *** DEADLOCK ***

1 lock held by syz.0.25/4374:
 #0: ffff88807b60a6a0 (sk_lock-AF_PHONET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
 #0: ffff88807b60a6a0 (sk_lock-AF_PHONET){+.+.}-{0:0}, at: pep_sock_accept+0xb5/0x1190 net/phonet/pep.c:779

stack backtrace:
CPU: 0 PID: 4374 Comm: syz.0.25 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
 mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
 mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
 mark_usage kernel/locking/lockdep.c:-1 [inline]
 __lock_acquire+0xd47/0x7d10 kernel/locking/lockdep.c:4966
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 _raw_spin_lock_nested+0x2e/0x40 kernel/locking/spinlock.c:368
 __sk_receive_skb+0x17b/0x980 net/core/sock.c:517
 sk_backlog_rcv include/net/sock.h:1080 [inline]
 __release_sock+0x1e1/0x450 net/core/sock.c:2731
 release_sock+0x5b/0x1b0 net/core/sock.c:3274
 pep_sock_accept+0xc73/0x1190 net/phonet/pep.c:878
 pn_socket_accept+0x126/0x360 net/phonet/socket.c:304
 do_accept+0x509/0x6f0 net/socket.c:1809
 __sys_accept4_file net/socket.c:1852 [inline]
 __sys_accept4+0x103/0x170 net/socket.c:1882
 __do_sys_accept4 net/socket.c:1894 [inline]
 __se_sys_accept4 net/socket.c:1891 [inline]
 __x64_sys_accept4+0x96/0xb0 net/socket.c:1891
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f70192b8819
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:00007f70188f9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000120
RAX: ffffffffffffffda RBX: 00007f7019532090 RCX: 00007f70192b8819
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f701934ec91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000080000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7019532128 R14: 00007f7019532090 R15: 00007ffcf52f7108
 </TASK>

Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/21 03:00 linux-5.15.y b9d57c40a767 e65da4ee .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/25 04:27 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/23 23:19 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/23 23:12 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/23 18:28 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/23 18:28 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/23 18:22 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/20 22:50 linux-5.15.y b9d57c40a767 e65da4ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.