syzbot


possible deadlock in ax25_device_event

Status: upstream: reported C repro on 2025/02/23 00:49
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+2fe6437a4558c0a468dd@syzkaller.appspotmail.com
First crash: 189d, last: 17h06m
Bug presence (2)
Date Name Commit Repro Result
2025/08/20 linux-5.15.y (ToT) c79648372d02 C [report] possible deadlock in ax25_device_event
2025/08/20 upstream (ToT) b19a97d57c15 C Didn't crash
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ax25_device_event (2) hams 4 1 275d 275d 0/29 closed as invalid on 2025/01/15 12:30
upstream possible deadlock in ax25_device_event hams 4 1 474d 474d 0/29 closed as invalid on 2024/06/03 15:58

Sample crash report:
device bpq0 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_CHANGE): bpq0: link becomes ready
======================================================
WARNING: possible circular locking dependency detected
5.15.189-syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4170 is trying to acquire lock:
ffff0000d7c0d120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
ffff0000d7c0d120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_kill_by_device net/ax25/af_ax25.c:99 [inline]
ffff0000d7c0d120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_device_event+0x20c/0x590 net/ax25/af_ax25.c:142

but task is already holding lock:
ffff80001629c1e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (rtnl_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743
       rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72
       ax25_setsockopt+0x870/0xa5c net/ax25/af_ax25.c:676
       __sys_setsockopt+0x260/0x36c net/socket.c:2203
       __do_sys_setsockopt net/socket.c:2214 [inline]
       __se_sys_setsockopt net/socket.c:2211 [inline]
       __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2211
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #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+0x2928/0x651c kernel/locking/lockdep.c:5012
       lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
       lock_sock_nested+0xd8/0x1d4 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+0x20c/0x590 net/ax25/af_ax25.c:142
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
       call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       dev_close_many+0x2cc/0x440 net/core/dev.c:1650
       dev_close+0x148/0x1f8 net/core/dev.c:1672
       bpq_device_event+0x318/0x824 drivers/net/hamradio/bpqether.c:548
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
       call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       dev_close_many+0x2cc/0x440 net/core/dev.c:1650
       dev_close+0x148/0x1f8 net/core/dev.c:1672
       bond_setup_by_slave+0x70/0x318 drivers/net/bonding/bond_main.c:1471
       bond_enslave+0x624/0x3014 drivers/net/bonding/bond_main.c:1855
       bond_do_ioctl+0x6ec/0xb3c drivers/net/bonding/bond_main.c:4238
       bond_siocdevprivate+0x18c/0x1dc drivers/net/bonding/bond_main.c:-1
       dev_siocdevprivate net/core/dev_ioctl.c:285 [inline]
       dev_ifsioc+0xa30/0xef4 net/core/dev_ioctl.c:403
       dev_ioctl+0x550/0xc94 net/core/dev_ioctl.c:612
       sock_ioctl+0x7e0/0x87c net/socket.c:1184
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl fs/ioctl.c:860 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

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.0.17/4170:
 #0: ffff80001629c1e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72

stack backtrace:
CPU: 0 PID: 4170 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2011
 check_noncircular+0x240/0x2d4 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+0x2928/0x651c kernel/locking/lockdep.c:5012
 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
 lock_sock_nested+0xd8/0x1d4 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+0x20c/0x590 net/ax25/af_ax25.c:142
 notifier_call_chain kernel/notifier.c:83 [inline]
 raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
 call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
 call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
 call_netdevice_notifiers net/core/dev.c:2075 [inline]
 dev_close_many+0x2cc/0x440 net/core/dev.c:1650
 dev_close+0x148/0x1f8 net/core/dev.c:1672
 bpq_device_event+0x318/0x824 drivers/net/hamradio/bpqether.c:548
 notifier_call_chain kernel/notifier.c:83 [inline]
 raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
 call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
 call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
 call_netdevice_notifiers net/core/dev.c:2075 [inline]
 dev_close_many+0x2cc/0x440 net/core/dev.c:1650
 dev_close+0x148/0x1f8 net/core/dev.c:1672
 bond_setup_by_slave+0x70/0x318 drivers/net/bonding/bond_main.c:1471
 bond_enslave+0x624/0x3014 drivers/net/bonding/bond_main.c:1855
 bond_do_ioctl+0x6ec/0xb3c drivers/net/bonding/bond_main.c:4238
 bond_siocdevprivate+0x18c/0x1dc drivers/net/bonding/bond_main.c:-1
 dev_siocdevprivate net/core/dev_ioctl.c:285 [inline]
 dev_ifsioc+0xa30/0xef4 net/core/dev_ioctl.c:403
 dev_ioctl+0x550/0xc94 net/core/dev_ioctl.c:612
 sock_ioctl+0x7e0/0x87c net/socket.c:1184
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl fs/ioctl.c:860 [inline]
 __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
8021q: adding VLAN 0 to HW filter on device bond0
bond0: (slave rose0): Enslaving as an active interface with an up link

Crashes (115):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/03 18:50 linux-5.15.y c79648372d02 7368264b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/08/30 22:30 linux-5.15.y 01879f56bdde 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/08/28 12:49 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/08/17 19:49 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/08/13 03:49 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/24 19:00 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/24 19:00 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/22 04:07 linux-5.15.y c79648372d02 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/18 19:19 linux-5.15.y c79648372d02 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/17 00:53 linux-5.15.y 89950c454265 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/16 13:34 linux-5.15.y 89950c454265 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/12 17:37 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/10 22:13 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/05 17:17 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/05 14:19 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
2025/07/02 19:05 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ax25_device_event
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/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/08/17 22:36 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/08/07 15:27 linux-5.15.y c79648372d02 04cffc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/08/03 16:08 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/30 23:54 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/26 22:18 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/16 00:20 linux-5.15.y 89950c454265 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/14 04:55 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/06 11:30 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/04 03:48 linux-5.15.y 3dea0e7f549e 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/03 21:45 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/02 12:16 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/02 11:16 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/02 08:47 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ax25_device_event
2025/07/01 19:00 linux-5.15.y 3dea0e7f549e 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 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
* Struck through repros no longer work on HEAD.