syzbot


possible deadlock in ax25_device_event

Status: upstream: reported on 2025/02/23 00:49
Reported-by: syzbot+2fe6437a4558c0a468dd@syzkaller.appspotmail.com
First crash: 128d, last: 21h28m
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ax25_device_event (2) hams 1 214d 214d 0/29 closed as invalid on 2025/01/15 12:30
upstream possible deadlock in ax25_device_event hams 1 413d 413d 0/29 closed as invalid on 2024/06/03 15:58

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
5.15.186-syzkaller #0 Not tainted
------------------------------------------------------
syz.1.1260/9771 is trying to acquire lock:
ffff8880734cc120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
ffff8880734cc120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_kill_by_device net/ax25/af_ax25.c:99 [inline]
ffff8880734cc120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_device_event+0x217/0x4f0 net/ax25/af_ax25.c:142

but task is already holding lock:
ffffffff8d22a808 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x54e/0xe50 net/core/dev_ioctl.c:586

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (rtnl_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       ax25_setsockopt+0x830/0xa40 net/ax25/af_ax25.c:676
       __sys_setsockopt+0x3d6/0x5e0 net/socket.c:2203
       __do_sys_setsockopt net/socket.c:2214 [inline]
       __se_sys_setsockopt net/socket.c:2211 [inline]
       __x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2211
       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

-> #0 (sk_lock-AF_AX25){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       lock_sock_nested+0x44/0x100 net/core/sock.c:3251
       lock_sock include/net/sock.h:1694 [inline]
       ax25_kill_by_device net/ax25/af_ax25.c:99 [inline]
       ax25_device_event+0x217/0x4f0 net/ax25/af_ax25.c:142
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xcb/0x160 kernel/notifier.c:391
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       __dev_notify_flags+0x178/0x2d0 net/core/dev.c:-1
       dev_change_flags+0xe3/0x1a0 net/core/dev.c:8929
       dev_ifsioc+0x147/0xe70 net/core/dev_ioctl.c:324
       dev_ioctl+0x55f/0xe50 net/core/dev_ioctl.c:587
       sock_do_ioctl+0x222/0x2f0 net/socket.c:1154
       sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       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

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(rtnl_mutex);
                               lock(sk_lock-AF_AX25);
                               lock(rtnl_mutex);
  lock(sk_lock-AF_AX25);

 *** DEADLOCK ***

1 lock held by syz.1.1260/9771:
 #0: ffffffff8d22a808 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x54e/0xe50 net/core/dev_ioctl.c:586

stack backtrace:
CPU: 0 PID: 9771 Comm: syz.1.1260 Not tainted 5.15.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 lock_sock_nested+0x44/0x100 net/core/sock.c:3251
 lock_sock include/net/sock.h:1694 [inline]
 ax25_kill_by_device net/ax25/af_ax25.c:99 [inline]
 ax25_device_event+0x217/0x4f0 net/ax25/af_ax25.c:142
 notifier_call_chain kernel/notifier.c:83 [inline]
 raw_notifier_call_chain+0xcb/0x160 kernel/notifier.c:391
 call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
 call_netdevice_notifiers net/core/dev.c:2075 [inline]
 __dev_notify_flags+0x178/0x2d0 net/core/dev.c:-1
 dev_change_flags+0xe3/0x1a0 net/core/dev.c:8929
 dev_ifsioc+0x147/0xe70 net/core/dev_ioctl.c:324
 dev_ioctl+0x55f/0xe50 net/core/dev_ioctl.c:587
 sock_do_ioctl+0x222/0x2f0 net/socket.c:1154
 sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
 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:0x7f30fdc90929
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:00007f30fbaf8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f30fdeb7fa0 RCX: 00007f30fdc90929
RDX: 0000200000000000 RSI: 0000000000008914 RDI: 0000000000000004
RBP: 00007f30fdd12b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f30fdeb7fa0 R15: 00007ffd2afb57b8
 </TASK>

Crashes (75):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/30 05:18 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/17 10:40 linux-5.15.y 1c700860e8bc cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/14 07:48 linux-5.15.y 1c700860e8bc 0e8da31f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/14 06:14 linux-5.15.y 1c700860e8bc 0e8da31f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/12 22:58 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/10 00:13 linux-5.15.y 1c700860e8bc 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/02 04:58 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/01 18:19 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/30 14:42 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/28 22:24 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/28 10:51 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/28 10:51 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/26 21:12 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/26 21:12 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/26 19:51 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/26 00:29 linux-5.15.y 98f47d0e9b8c 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/26 00:06 linux-5.15.y 98f47d0e9b8c 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/24 08:06 linux-5.15.y 98f47d0e9b8c ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/24 08:03 linux-5.15.y 98f47d0e9b8c ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/22 05:45 linux-5.15.y a68c15152131 0919b50b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/21 06:44 linux-5.15.y a68c15152131 b47f9e02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/21 06:44 linux-5.15.y a68c15152131 b47f9e02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/18 18:25 linux-5.15.y a68c15152131 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/16 06:22 linux-5.15.y 3b8db0e4f263 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/11 04:53 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/10 03:43 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/10 01:26 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/10 01:26 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/05/08 15:40 linux-5.15.y 16fdf2c7111b dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/04/16 22:41 linux-5.15.y f7347f400572 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/04/08 20:53 linux-5.15.y 0c935c049b5c a775275d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/03/28 00:00 linux-5.15.y 0c935c049b5c 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/02/26 09:46 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/02/23 00:48 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/02/23 00:48 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/06/30 04:17 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/27 17:03 linux-5.15.y 3dea0e7f549e 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/24 11:44 linux-5.15.y 1c700860e8bc e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/18 05:01 linux-5.15.y 1c700860e8bc e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/13 04:56 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/12 22:55 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/09 23:01 linux-5.15.y 1c700860e8bc 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/09 18:58 linux-5.15.y 1c700860e8bc 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/08 00:06 linux-5.15.y 1c700860e8bc 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/06/02 18:04 linux-5.15.y 98f47d0e9b8c b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/30 13:28 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/30 08:38 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/28 11:01 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/28 10:59 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/26 02:25 linux-5.15.y 98f47d0e9b8c 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/24 07:35 linux-5.15.y 98f47d0e9b8c ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/23 13:21 linux-5.15.y 98f47d0e9b8c fa44301a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/21 05:18 linux-5.15.y a68c15152131 b47f9e02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/21 05:17 linux-5.15.y a68c15152131 b47f9e02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/18 18:22 linux-5.15.y a68c15152131 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/18 18:20 linux-5.15.y a68c15152131 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/16 06:36 linux-5.15.y 3b8db0e4f263 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/09 20:07 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/05/09 20:07 linux-5.15.y 3b8db0e4f263 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/04/13 10:15 linux-5.15.y f7347f400572 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/04/09 15:25 linux-5.15.y 0c935c049b5c 47d015b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/04/04 04:22 linux-5.15.y 0c935c049b5c d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
* Struck through repros no longer work on HEAD.