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
Fix commit: b2606c302d7f phonet/pep: disable BH around forwarded sk_receive_skb()
Patched on: [ci2-linux-5-15-kasan ci2-linux-5-15-kasan-perf], missing on: [ci2-linux-5-15-kasan-arm64]
First crash: 111d, last: 3h41m
Fix bisection: fixed by (bisect log) :
commit b2606c302d7f2b4ee48da05e32ed60aed1b0cd53
Author: Zijing Yin <yzjaurora@gmail.com>
Date: Tue May 19 17:26:33 2026 +0000

  phonet/pep: disable BH around forwarded sk_receive_skb()

  
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 (12)
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 661d 879d 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 21 9h33m 4d14h 0/2 upstream: reported on 2026/08/05 10:00
linux-6.6 inconsistent lock state in valid_state origin:upstream 4 syz, C done 19 73d 113d 2/2 fixed on 2026/06/29 10:59
upstream inconsistent lock state in valid_state (6) kernfs comedi 4 2 295d 294d 0/29 auto-obsoleted due to no activity on 2026/01/26 19:03
upstream inconsistent lock state in valid_state kernel 4 1 1263d 1259d 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 545d 720d 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 1152d 1231d 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 376 7h42m 1052d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (5) net 4 515 340d 344d 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 790d 915d 25/29 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm 4 syz, C error 376 737d 786d 27/29 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 4 1 1232d 1232d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/06/10 06:45 22m retest repro linux-5.15.y OK log
2026/06/10 06:45 22m retest repro linux-5.15.y OK log
2026/06/10 06:45 23m retest repro linux-5.15.y OK log
2026/06/10 06:45 23m retest repro linux-5.15.y OK log
2026/06/10 06:45 36m retest repro linux-5.15.y OK log
2026/06/09 16:45 24m retest repro linux-5.15.y OK log
2026/06/09 16:45 24m retest repro linux-5.15.y OK log
2026/06/09 16:45 43m retest repro linux-5.15.y OK log
2026/06/09 16:45 35m retest repro linux-5.15.y OK log
2026/06/09 16:45 29m retest repro linux-5.15.y OK log

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/1/20 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888146920120
 (
sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x83/0x120 net/x25/af_x25.c:1777
{SOFTIRQ-ON-W} state was registered at:
  lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
  lock_sock_nested+0x44/0x100 net/core/sock.c:3259
  lock_sock include/net/sock.h:1744 [inline]
  x25_bind+0x18a/0x3b0 net/x25/af_x25.c:698
  __sys_bind+0x2e9/0x3e0 net/socket.c:1730
  __do_sys_bind net/socket.c:1741 [inline]
  __se_sys_bind net/socket.c:1739 [inline]
  __x64_sys_bind+0x76/0x80 net/socket.c:1739
  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
irq event stamp: 444236
hardirqs last  enabled at (444236): [<ffffffff814926e6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (444235): [<ffffffff81492687>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last  enabled at (444200): [<ffffffff814951c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
softirqs last disabled at (444205): [<ffffffff814951c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943

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 ***

1 lock held by ksoftirqd/1/20:
 #0: ffffffff8c31ef60 (
rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313

stack backtrace:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/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+0xc63/0x7b50 kernel/locking/lockdep.c:4966
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 lock_sock_nested+0x44/0x100 net/core/sock.c:3259
 lock_sock include/net/sock.h:1744 [inline]
 x25_kill_by_neigh+0x83/0x120 net/x25/af_x25.c:1777
 x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
 __netif_receive_skb_one_core net/core/dev.c:5551 [inline]
 netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
 lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
 __napi_poll+0xbb/0x430 net/core/dev.c:7101
 napi_poll net/core/dev.c:7168 [inline]
 net_rx_action+0x522/0xa80 net/core/dev.c:7258
 handle_softirqs+0x336/0x830 kernel/softirq.c:576
 run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
 smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3261
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 20, name: ksoftirqd/1
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff81492a7d>] softirq_handle_begin kernel/softirq.c:414 [inline]
[<ffffffff81492a7d>] handle_softirqs+0xfd/0x830 kernel/softirq.c:552
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 ___might_sleep+0x493/0x610 kernel/sched/core.c:9658
 lock_sock_nested+0x5b/0x100 net/core/sock.c:3261
 lock_sock include/net/sock.h:1744 [inline]
 x25_kill_by_neigh+0x83/0x120 net/x25/af_x25.c:1777
 x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
 __netif_receive_skb_one_core net/core/dev.c:5551 [inline]
 netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
 lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
 __napi_poll+0xbb/0x430 net/core/dev.c:7101
 napi_poll net/core/dev.c:7168 [inline]
 net_rx_action+0x522/0xa80 net/core/dev.c:7258
 handle_softirqs+0x336/0x830 kernel/softirq.c:576
 run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
 smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (67):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/09 20:29 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/09 06:41 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/08 07:15 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/08 07:14 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/07 14:43 linux-5.15.y aabd761612db e4ef95d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/07 13:33 linux-5.15.y aabd761612db e4ef95d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/06 22:39 linux-5.15.y 9c7634c60784 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/06 21:22 linux-5.15.y 9c7634c60784 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/06 08:59 linux-5.15.y 6e2fd6534337 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/06 00:13 linux-5.15.y 6e2fd6534337 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/05 22:04 linux-5.15.y 6e2fd6534337 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/05 02:04 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 19:19 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 19:11 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 16:42 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 16:36 linux-5.15.y 6e2fd6534337 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 02:08 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 02:08 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 02:08 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 02:07 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/04 02:07 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 11:43 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 10:33 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 09:18 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 08:01 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 04:32 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 02:41 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/22 22:15 linux-5.15.y 93741761e5e3 5f091fcc .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/22 09:11 linux-5.15.y 93741761e5e3 70ae9b03 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 20:51 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 20:40 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 16:08 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 16:06 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 15:56 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/13 15:55 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/07 07:21 linux-5.15.y ef251c45f1cd f250db59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/05 06:42 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/05 04:10 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/05 04:04 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/05 04:00 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/04 17:57 linux-5.15.y ef251c45f1cd 85f1bcf2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/03 16:07 linux-5.15.y ef251c45f1cd a0d91488 .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/28 01:34 linux-5.15.y b9d57c40a767 ce741359 .config console log report info [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/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/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.