possible deadlock in __dev_queue_xmit (2)

Status: upstream: reported on 2026/08/24 18:29
Reported-by: syzbot+d3df26b8b51bf068ed57@syzkaller.appspotmail.com
First crash: 4d00h, last: 58m
Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-49 possible deadlock in __dev_queue_xmit 4 4 2624d 2693d 0/3 auto-closed as invalid on 2019/10/25 08:36
upstream possible deadlock in __dev_queue_xmit (3) net 4 syz, C done inconclusive 1154 153d 2460d 0/29 upstream: reported C repro on 2019/12/03 09:55
linux-6.6 possible deadlock in __dev_queue_xmit 4 1 202d 202d 0/2 auto-obsoleted due to no activity on 2026/05/18 03:49
linux-6.1 possible deadlock in __dev_queue_xmit (4) 4 syz, C 46 1h01m 4d00h 0/3 upstream: reported C repro on 2026/08/24 18:32
linux-4.19 possible deadlock in __dev_queue_xmit 4 syz, C error 5 1801d 2219d 0/1 upstream: reported C repro on 2020/07/31 07:05
android-414 possible deadlock in __dev_queue_xmit 4 3 2682d 2693d 0/1 auto-closed as invalid on 2019/10/21 21:31
linux-6.1 possible deadlock in __dev_queue_xmit (3) 4 104 371d 672d 0/3 auto-obsoleted due to no activity on 2025/10/30 22:15
android-44 possible deadlock in __dev_queue_xmit 4 14 2459d 2521d 0/2 auto-closed as invalid on 2020/04/02 07:14
linux-6.1 possible deadlock in __dev_queue_xmit 4 98 1043d 1157d 0/3 auto-obsoleted due to no activity on 2023/12/28 22:22
linux-4.14 possible deadlock in __dev_queue_xmit 4 7 2169d 2614d 0/1 auto-closed as invalid on 2021/01/16 21:33
upstream possible deadlock in __dev_queue_xmit net 4 1 2782d 2782d 0/29 closed as invalid on 2019/03/10 18:51
linux-5.15 possible deadlock in __dev_queue_xmit 4 113 1108d 1244d 0/3 auto-obsoleted due to no activity on 2023/10/25 04:56
linux-6.1 possible deadlock in __dev_queue_xmit (2) 4 7 842d 952d 0/3 auto-obsoleted due to no activity on 2024/08/16 05:44
linux-5.15 possible deadlock in __dev_queue_xmit (2) origin:lts-only 4 syz, C done 219 5h10m 987d 0/3 upstream: reported C repro on 2023/12/15 02:11
upstream possible deadlock in __dev_queue_xmit (2) kernel 4 2 2594d 2710d 0/29 auto-closed as invalid on 2019/11/19 09:01

Sample crash report:
syzkaller0: entered promiscuous mode
syzkaller0: entered allmulticast mode
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.2.5591/23753 is trying to acquire lock:
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3918 [inline]
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_queue_xmit+0xb01/0x3640 net/core/dev.c:4434

but task is already holding lock:
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3918 [inline]
ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_queue_xmit+0xb01/0x3640 net/core/dev.c:4434

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

       CPU0
       ----
  lock(&sch->root_lock_key#600);
  lock(&sch->root_lock_key#600);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

3 locks held by syz.2.5591/23753:
 #0: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: local_bh_disable include/linux/bottom_half.h:20 [inline]
 #0: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_read_lock_bh include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: __dev_queue_xmit+0x275/0x3640 net/core/dev.c:4393
 #1: ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
 #1: ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3918 [inline]
 #1: ffff888074c30108 (&sch->root_lock_key#600){+...}-{2:2}, at: __dev_queue_xmit+0xb01/0x3640 net/core/dev.c:4434
 #2: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: local_bh_disable include/linux/bottom_half.h:20 [inline]
 #2: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_read_lock_bh include/linux/rcupdate.h:838 [inline]
 #2: ffffffff8d131e00 (rcu_read_lock_bh){....}-{1:2}, at: __dev_queue_xmit+0x275/0x3640 net/core/dev.c:4393

stack backtrace:
CPU: 1 PID: 23753 Comm: syz.2.5591 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x6809/0x7d80 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:351 [inline]
 __dev_xmit_skb net/core/dev.c:3918 [inline]
 __dev_queue_xmit+0xb01/0x3640 net/core/dev.c:4434
 sch_frag_xmit_hook+0x2a8/0x11d0 net/sched/sch_frag.c:148
 tcf_mirred_forward net/sched/act_mirred.c:215 [inline]
 tcf_mirred_to_dev net/sched/act_mirred.c:-1 [inline]
 tcf_mirred_act+0xbd6/0x1350 net/sched/act_mirred.c:337
 tc_act include/net/tc_wrapper.h:221 [inline]
 tcf_action_exec+0x1a9/0x5d0 net/sched/act_api.c:1097
 tcf_exts_exec include/net/pkt_cls.h:363 [inline]
 basic_classify+0x1b2/0x2d0 net/sched/cls_basic.c:54
 tc_classify include/net/tc_wrapper.h:227 [inline]
 __tcf_classify net/sched/cls_api.c:1754 [inline]
 tcf_classify+0x421/0xfc0 net/sched/cls_api.c:1850
 qfq_classify net/sched/sch_qfq.c:715 [inline]
 qfq_enqueue+0x320/0x12e0 net/sched/sch_qfq.c:1239
 dev_qdisc_enqueue+0x48/0x220 net/core/dev.c:3854
 __dev_xmit_skb net/core/dev.c:3943 [inline]
 __dev_queue_xmit+0xcd4/0x3640 net/core/dev.c:4434
 packet_snd net/packet/af_packet.c:3161 [inline]
 packet_sendmsg+0x38d9/0x4a30 net/packet/af_packet.c:3193
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg net/socket.c:745 [inline]
 ____sys_sendmsg+0x61b/0x980 net/socket.c:2595
 ___sys_sendmsg+0x2a6/0x360 net/socket.c:2649
 __sys_sendmsg net/socket.c:2678 [inline]
 __do_sys_sendmsg net/socket.c:2687 [inline]
 __se_sys_sendmsg+0x1d0/0x2c0 net/socket.c:2685
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0e7b19e159
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:00007f0e7c149028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f0e7b425fa0 RCX: 00007f0e7b19e159
RDX: 0000000000004005 RSI: 0000200000000280 RDI: 0000000000000006
RBP: 00007f0e7b235024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0e7b426038 R14: 00007f0e7b425fa0 R15: 00007ffcc2e51208
 </TASK>

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/28 18:03 linux-6.6.y a4a971135a2f e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/28 18:03 linux-6.6.y a4a971135a2f e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/28 13:42 linux-6.6.y a4a971135a2f e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/28 13:42 linux-6.6.y a4a971135a2f e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 21:14 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 21:14 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 21:07 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 21:07 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 16:12 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 16:12 linux-6.6.y dc6160265ffc a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 10:19 linux-6.6.y dc6160265ffc 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 10:19 linux-6.6.y dc6160265ffc 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/25 08:12 linux-6.6.y dc6160265ffc 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/24 18:30 linux-6.6.y dc6160265ffc b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/24 18:30 linux-6.6.y dc6160265ffc b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
2026/08/24 18:29 linux-6.6.y dc6160265ffc b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __dev_queue_xmit
* Struck through repros no longer work on HEAD.