linux-kernel - [syzbot] [wireless?] WARNING in ieee80211_set_active

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68b11398.a00a0220.1337b0.0012.GAE@google.com>
Date: Thu, 28 Aug 2025 19:42:32 -0700
From: syzbot <syzbot+ab36888b82c02205065e@...kaller.appspotmail.com>
To: johannes@...solutions.net, linux-kernel@...r.kernel.org, 
	linux-wireless@...r.kernel.org, netdev@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [wireless?] WARNING in ieee80211_set_active_links (2)

Hello,

syzbot found the following issue on:

HEAD commit:    69fd6b99b8f8 Merge tag 'perf_urgent_for_v6.17_rc3' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167a6c42580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fecbb496f75d3d61
dashboard link: https://syzkaller.appspot.com/bug?extid=ab36888b82c02205065e
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0010173ae06b/disk-69fd6b99.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/015ec9f0bead/vmlinux-69fd6b99.xz
kernel image: https://storage.googleapis.com/syzbot-assets/402b824d5994/bzImage-69fd6b99.xz

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

------------[ cut here ]------------
wlan0: Failed check-sdata-in-driver check, flags: 0x0
WARNING: CPU: 0 PID: 21522 at net/mac80211/driver-ops.h:1723 drv_can_activate_links net/mac80211/driver-ops.h:1723 [inline]
WARNING: CPU: 0 PID: 21522 at net/mac80211/driver-ops.h:1723 ieee80211_set_active_links+0x2d5/0x9d0 net/mac80211/link.c:600
Modules linked in:
CPU: 0 UID: 0 PID: 21522 Comm: kworker/u10:0 Tainted: G     U              syzkaller #0 PREEMPT(full) 
Tainted: [U]=USER
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:drv_can_activate_links net/mac80211/driver-ops.h:1723 [inline]
RIP: 0010:ieee80211_set_active_links+0x2d5/0x9d0 net/mac80211/link.c:600
Code: 74 24 08 48 81 c6 20 01 00 00 48 89 74 24 08 e8 91 13 b5 f6 8b 54 24 04 48 8b 74 24 08 48 c7 c7 20 eb 08 8d e8 0c 0c 74 f6 90 <0f> 0b 90 90 e8 72 13 b5 f6 4c 89 e2 48 b8 00 00 00 00 00 fc ff df
RSP: 0018:ffffc90003c3fb00 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff888143bda9d0 RCX: ffffffff817a02c8
RDX: ffff888079fa3c00 RSI: ffffffff817a02d5 RDI: 0000000000000001
RBP: 000000000000000a R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: fffffffffffdf818 R12: ffff888143bd9728
R13: 0000000000000000 R14: ffff8880280e0e40 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8881246c3000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000001f2000 CR3: 0000000056f24000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ieee80211_if_parse_active_links+0xbb/0x120 net/mac80211/debugfs_netdev.c:733
 wiphy_locked_debugfs_write_work+0xe6/0x1c0 net/wireless/debugfs.c:215
 cfg80211_wiphy_work+0x2c7/0x580 net/wireless/core.c:435
 process_one_work+0x9cf/0x1b70 kernel/workqueue.c:3236
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
 kthread+0x3c5/0x780 kernel/kthread.c:463
 ret_from_fork+0x5d4/0x6f0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


---
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@...glegroups.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 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