netdev - [syzbot] [wireless?] WARNING in ieee80211_request_ibss

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: <677d5577.050a0220.a40f5.0022.GAE@google.com>
Date: Tue, 07 Jan 2025 08:25:27 -0800
From: syzbot <syzbot+1634c5399e29d8b66789@...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_request_ibss_scan

Hello,

syzbot found the following issue on:

HEAD commit:    63676eefb7a0 Merge tag 'sched_ext-for-6.13-rc5-fixes' of g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17e98edf980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=86dd15278dbfe19f
dashboard link: https://syzkaller.appspot.com/bug?extid=1634c5399e29d8b66789
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-63676eef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/efc20deb6462/vmlinux-63676eef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b916a2c594d7/bzImage-63676eef.xz

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

wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
------------[ cut here ]------------
WARNING: CPU: 2 PID: 94 at net/mac80211/scan.c:1213 ieee80211_request_ibss_scan+0x7b8/0x9a0 net/mac80211/scan.c:1213
Modules linked in:
CPU: 2 UID: 0 PID: 94 Comm: kworker/u32:5 Not tainted 6.13.0-rc5-syzkaller-00161-g63676eefb7a0 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:ieee80211_request_ibss_scan+0x7b8/0x9a0 net/mac80211/scan.c:1213
Code: e9 3b fb ff ff e8 08 ce 08 f7 be 04 00 00 00 bf 06 00 00 00 41 bd 04 00 00 00 e8 33 d0 08 f7 e9 3b fd ff ff e8 e9 cd 08 f7 90 <0f> 0b 90 bb ea ff ff ff e9 6e fc ff ff 48 c7 c7 d4 1a 1d 90 e8 ef
RSP: 0018:ffffc900010af988 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8a908130
RDX: ffff88801f83a440 RSI: ffffffff8a9081c7 RDI: 0000000000000005
RBP: ffff888064659720 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000003 R12: 0000000000000005
R13: 0000000000000006 R14: dffffc0000000000 R15: ffff88804ff70e40
FS:  0000000000000000(0000) GS:ffff88802b600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002f61bffc CR3: 000000001e3c2000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ieee80211_sta_merge_ibss net/mac80211/ibss.c:1290 [inline]
 ieee80211_ibss_work+0x83b/0x14c0 net/mac80211/ibss.c:1672
 ieee80211_iface_work+0xd01/0xf00 net/mac80211/iface.c:1689
 cfg80211_wiphy_work+0x3de/0x560 net/wireless/core.c:440
 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229
 process_scheduled_works kernel/workqueue.c:3310 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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