[syzbot] [wireless?] WARNING in ieee80211_queue_skb

[syzbot] [wireless?] WARNING in ieee80211_queue_skb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    20a33c6b6cbe Add linux-next specific files for 20261023
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf1aa5580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=82b79abce6d1b17c
dashboard link: https://syzkaller.appspot.com/bug?extid=c38f93f387ac25eabf68
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=117f4d8e580000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c38f93f387ac25eabf68@syzkaller.appspotmail.com

------------[ cut here ]------------
syzkaller0: Failed check-sdata-in-driver check, flags: 0x0
WARNING: net/mac80211/driver-ops.h:1380 at drv_wake_tx_queue net/mac80211/driver-ops.h:1380 [inline], CPU#1: syz-executor116/6060
WARNING: net/mac80211/driver-ops.h:1380 at schedule_and_wake_txq net/mac80211/driver-ops.h:1391 [inline], CPU#1: syz-executor116/6060
WARNING: net/mac80211/driver-ops.h:1380 at ieee80211_queue_skb+0x1cb4/0x22e0 net/mac80211/tx.c:1729, CPU#1: syz-executor116/6060
Modules linked in:
CPU: 1 UID: 0 PID: 6060 Comm: syz-executor116 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
RIP: 0010:drv_wake_tx_queue net/mac80211/driver-ops.h:1380 [inline]
RIP: 0010:schedule_and_wake_txq net/mac80211/driver-ops.h:1391 [inline]
RIP: 0010:ieee80211_queue_skb+0x1cfc/0x22e0 net/mac80211/tx.c:1729
Code: 00 00 48 85 c0 4c 0f 44 e5 48 b8 00 00 00 00 00 fc ff df 41 0f b6 44 05 00 84 c0 0f 85 6d 04 00 00 41 8b 16 4c 89 ff 4c 89 e6 <67> 48 0f b9 3a 49 bf 00 00 00 00 00 fc ff df e9 b5 fa ff ff e8 bb
RSP: 0018:ffffc90003316f70 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88805ac32d90 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: ffff88805ac30120 RDI: ffffffff91d2d970
RBP: ffff88805ac319f0 R08: ffffffff91c0abbf R09: 1ffffffff2381577
R10: dffffc0000000000 R11: fffffbfff2381578 R12: ffff88805ac30120
R13: 1ffff1100b58633c R14: ffff88805ac319e0 R15: ffffffff91d2d970
FS:  00007f837dd626c0(0000) GS:ffff88812347c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f837e562ff8 CR3: 0000000013544000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 __ieee80211_xmit_fast+0x8ea/0x2160 net/mac80211/tx.c:3862
 ieee80211_xmit_fast net/mac80211/tx.c:3930 [inline]
 __ieee80211_subif_start_xmit+0x1367/0x1840 net/mac80211/tx.c:4489
 ieee80211_subif_start_xmit+0xee/0x560 net/mac80211/tx.c:4726
 __netdev_start_xmit include/linux/netdevice.h:5455 [inline]
 netdev_start_xmit include/linux/netdevice.h:5464 [inline]
 xmit_one net/core/dev.c:4057 [inline]
 dev_hard_start_xmit+0x2cd/0x830 net/core/dev.c:4073
 __dev_queue_xmit+0x14d1/0x3920 net/core/dev.c:5066
 packet_snd net/packet/af_packet.c:3157 [inline]
 packet_sendmsg+0x3f1b/0x51b0 net/packet/af_packet.c:3189
 sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800
 __sock_sendmsg net/socket.c:818 [inline]
 __sys_sendto+0x408/0x5a0 net/socket.c:2283
 __do_sys_sendto net/socket.c:2290 [inline]
 __se_sys_sendto net/socket.c:2286 [inline]
 __x64_sys_sendto+0xde/0x100 net/socket.c:2286
 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
RIP: 0033:0x7f837e5c51de
Code: 08 0f 85 f5 e2 ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 90 41 57 41 56 4d 89 c6 41 55 4d 89 cd 41 54 55 53 48 83 ec 08
RSP: 002b:00007f837dd620b8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00007f837dd626c0 RCX: 00007f837e5c51de
RDX: 000000000000003c RSI: 00007f837dd62140 RDI: 0000000000000004
RBP: 00007f837dd62120 R08: 00007f837dd62120 R09: 0000000000000014
R10: 0000000000000040 R11: 0000000000000246 R12: 00007f837dd62180
R13: 0000000000000013 R14: 00007ffe6cb13b50 R15: 00007ffe6cb13c38
 </TASK>
----------------
Code disassembly (best guess):
   0:	00 00                	add    %al,(%rax)
   2:	48 85 c0             	test   %rax,%rax
   5:	4c 0f 44 e5          	cmove  %rbp,%r12
   9:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  10:	fc ff df
  13:	41 0f b6 44 05 00    	movzbl 0x0(%r13,%rax,1),%eax
  19:	84 c0                	test   %al,%al
  1b:	0f 85 6d 04 00 00    	jne    0x48e
  21:	41 8b 16             	mov    (%r14),%edx
  24:	4c 89 ff             	mov    %r15,%rdi
  27:	4c 89 e6             	mov    %r12,%rsi
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	49 bf 00 00 00 00 00 	movabs $0xdffffc0000000000,%r15
  36:	fc ff df
  39:	e9 b5 fa ff ff       	jmp    0xfffffaf3
  3e:	e8                   	.byte 0xe8
  3f:	bb                   	.byte 0xbb


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup