inconsistent lock state in valid_state (7)

Status: upstream: reported C repro on 2026/08/11 00:12
Subsystems: x25
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+15cbd86f569e8b084383@syzkaller.appspotmail.com
First crash: 23d, last: 22h20m
✨ AI Patch Versions (1)
Version Stage Reported Report Link Job
1 moderation 2026/08/11 11:29 Discussion 52927852-8f6a-44c7-84a5-8eca5340fc99
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
52927852 patching inconsistent lock state in valid_state (7) 2026/08/11 10:05 2026/08/11 10:05 2026/08/11 11:29 508909ea
4ecb9a6a assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ✅ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ❌ VMGuestTrigger: ✅ VMHostTrigger: ❌ inconsistent lock state in valid_state (7) 2026/08/08 23:23 2026/08/08 23:23 2026/08/09 00:11 5d63f80b
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [x25?] inconsistent lock state in valid_state (7) 0 (3) 2026/08/28 19:34
Similar bugs (13)
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 syz, C done 208 681d 899d 0/3 auto-obsoleted due to no activity on 2024/12/26 10:49
linux-6.6 inconsistent lock state in valid_state (2) 4 syz, C 54 2d05h 24d 0/2 upstream: reported C repro on 2026/08/05 10:00
linux-6.6 inconsistent lock state in valid_state origin:upstream 4 syz, C done 19 93d 133d 2/2 fixed on 2026/06/29 10:59
linux-5.15 inconsistent lock state in valid_state (3) origin:upstream 4 syz, C done 303 1d13h 131d 2/3 upstream: reported C repro on 2026/04/20 22:51
upstream inconsistent lock state in valid_state (6) kernfs comedi 4 2 315d 314d 0/29 auto-obsoleted due to no activity on 2026/01/26 19:03
upstream inconsistent lock state in valid_state kernel 4 1 1283d 1279d 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 syz, C error 72 565d 740d 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 1172d 1251d 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 syz, C done 581 1d11h 1072d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (5) net 4 515 360d 364d 0/29 closed as invalid on 2025/09/16 17:45
upstream inconsistent lock state in valid_state (2) sound 4 syz, C inconclusive 57405 810d 935d 25/29 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm 4 syz, C error 376 757d 806d 27/29 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 4 1 1252d 1252d 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 {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/0/15 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff88807927c260 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
ffff88807927c260 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1778
{SOFTIRQ-ON-W} state was registered at:
  lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
  lock_sock_nested+0x41/0x100 net/core/sock.c:3827
  lock_sock include/net/sock.h:1713 [inline]
  x25_bind+0x209/0x450 net/x25/af_x25.c:694
  __sys_bind_socket net/socket.c:1945 [inline]
  __sys_bind+0x2e3/0x410 net/socket.c:1976
  __do_sys_bind net/socket.c:1981 [inline]
  __se_sys_bind net/socket.c:1979 [inline]
  __x64_sys_bind+0x7a/0x90 net/socket.c:1979
  do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
  do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
  entry_SYSCALL_64_after_hwframe+0x77/0x7f
irq event stamp: 699710
hardirqs last  enabled at (699710): [<ffffffff8188ed06>] __local_bh_enable_ip+0xd6/0x140 kernel/softirq.c:478
hardirqs last disabled at (699709): [<ffffffff8188eca2>] __local_bh_enable_ip+0x72/0x140 kernel/softirq.c:455
softirqs last  enabled at (699556): [<ffffffff818919e6>] run_ksoftirqd+0x36/0x60 kernel/softirq.c:1108
softirqs last disabled at (699561): [<ffffffff818919e6>] run_ksoftirqd+0x36/0x60 kernel/softirq.c:1108

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

       CPU0
       ----
  lock(sk_lock-AF_X25);
  <Interrupt>
    lock(sk_lock-AF_X25);

 *** DEADLOCK ***

locks held by ksoftirqd/0/15: 1, last CPU#0:
 #0: ffffffff8ed5c6e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #0: ffffffff8ed5c6e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8ed5c6e0 (rcu_read_lock){....}-{1:3}, at: netif_receive_skb_core+0x33/0x2b0 net/core/dev.c:6288

stack backtrace:
CPU: 0 UID: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_usage_bug+0x28c/0x2e0 kernel/locking/lockdep.c:4058
 valid_state+0xbe/0xf0 kernel/locking/lockdep.c:4072
 mark_lock_irq+0x36/0x380 kernel/locking/lockdep.c:4283
 mark_lock+0x117/0x190 kernel/locking/lockdep.c:4769
 mark_usage kernel/locking/lockdep.c:-1 [inline]
 __lock_acquire+0x6b7/0x2e50 kernel/locking/lockdep.c:5208
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
 lock_sock_nested+0x41/0x100 net/core/sock.c:3827
 lock_sock include/net/sock.h:1713 [inline]
 x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1778
 x25_lapb_receive_frame+0x1b0/0xfb0 net/x25/x25_dev.c:138
 __netif_receive_skb_one_core net/core/dev.c:6264 [inline]
 netif_receive_skb_core+0x2a6/0x2b0 net/core/dev.c:6289
 lapbeth_napi_poll+0x42/0x90 drivers/net/wan/lapbether.c:100
 __napi_poll+0xaa/0x330 net/core/dev.c:7787
 napi_poll net/core/dev.c:7850 [inline]
 net_rx_action+0x61d/0xf50 net/core/dev.c:8007
 handle_softirqs+0x226/0x860 kernel/softirq.c:645
 run_ksoftirqd+0x36/0x60 kernel/softirq.c:1108
 smpboot_thread_fn+0x565/0xa70 kernel/smpboot.c:160
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3829
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 15, name: ksoftirqd/0
preempt_count: 100, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8188ef0b>] softirq_handle_begin kernel/softirq.c:486 [inline]
[<ffffffff8188ef0b>] handle_softirqs+0xab/0x860 kernel/softirq.c:621
CPU: 0 UID: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 __might_resched+0x36a/0x4c0 kernel/sched/core.c:9234
 lock_sock_nested+0x56/0x100 net/core/sock.c:3829
 lock_sock include/net/sock.h:1713 [inline]
 x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1778
 x25_lapb_receive_frame+0x1b0/0xfb0 net/x25/x25_dev.c:138
 __netif_receive_skb_one_core net/core/dev.c:6264 [inline]
 netif_receive_skb_core+0x2a6/0x2b0 net/core/dev.c:6289
 lapbeth_napi_poll+0x42/0x90 drivers/net/wan/lapbether.c:100
 __napi_poll+0xaa/0x330 net/core/dev.c:7787
 napi_poll net/core/dev.c:7850 [inline]
 net_rx_action+0x61d/0xf50 net/core/dev.c:8007
 handle_softirqs+0x226/0x860 kernel/softirq.c:645
 run_ksoftirqd+0x36/0x60 kernel/softirq.c:1108
 smpboot_thread_fn+0x565/0xa70 kernel/smpboot.c:160
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (426):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/29 03:06 net 7e1d6caa9c6b bcbc8ceb .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2026/08/28 19:34 net-next 1b78070aaef6 bcbc8ceb .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce inconsistent lock state in valid_state
2026/08/14 13:12 linux-next 2697ef8943c9 b13552fe .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/11 08:23 linux-next 3d08ff75a47a 039457bd .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/27 20:00 upstream 18fbf5151d2c e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2026/08/29 01:08 net 7e1d6caa9c6b bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2026/08/28 16:29 net-next 1b78070aaef6 bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce inconsistent lock state in valid_state
2026/08/28 13:10 net-next 1b78070aaef6 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce inconsistent lock state in valid_state
2026/08/28 17:43 linux-next e30626823a40 bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/28 15:05 linux-next 3d83758432b5 bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/28 10:02 linux-next 3d83758432b5 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/28 07:38 linux-next 3d83758432b5 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/28 02:27 linux-next 3d83758432b5 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/27 17:27 linux-next 3d83758432b5 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/27 12:52 linux-next f82a5da2f049 a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/26 20:25 linux-next f82a5da2f049 a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/26 18:14 linux-next f82a5da2f049 a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/26 03:26 linux-next a8406e6c0b79 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/25 15:49 linux-next a8406e6c0b79 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/25 11:07 linux-next 4b18edbd8e70 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/25 11:05 linux-next 4b18edbd8e70 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/24 16:53 linux-next 4b18edbd8e70 23caa175 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/24 14:32 linux-next 903c1cf6dff9 23caa175 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/24 10:44 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/24 08:33 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 23:27 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 22:02 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 14:57 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 11:42 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 10:29 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/23 06:55 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/22 22:50 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/22 21:49 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/22 07:14 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/22 03:03 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/21 17:23 linux-next 903c1cf6dff9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/21 10:24 linux-next 7079a12d7506 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/21 09:20 linux-next 7079a12d7506 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/20 23:23 linux-next 7079a12d7506 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/20 16:39 linux-next 7079a12d7506 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/20 10:05 linux-next 6a746cd265ae 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/20 07:28 linux-next 6a746cd265ae 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/19 15:24 linux-next 6a746cd265ae 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/19 08:25 linux-next 5453bc3279e9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/19 00:10 linux-next 5453bc3279e9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/18 18:54 linux-next e6664f2b33db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/17 21:55 linux-next e6664f2b33db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/17 21:32 linux-next 4477a78374a5 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce inconsistent lock state in valid_state
2026/08/17 19:51 linux-next 4477a78374a5 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce inconsistent lock state in valid_state
2026/08/17 19:45 linux-next 4477a78374a5 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce inconsistent lock state in valid_state
2026/08/11 00:11 linux-next 3d08ff75a47a 039457bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/07 05:00 linux-next 1701fda2f58e c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2026/08/06 23:42 linux-next 1701fda2f58e c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.