netdev - [syzbot] WARNING: suspicious RCU usage in ieee80211_tx_h_select

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: <000000000000a095a405dc7878c5@google.com>
Date:   Tue, 12 Apr 2022 10:34:21 -0700
From:   syzbot <syzbot+e550ebeb0bc610768394@...kaller.appspotmail.com>
To:     davem@...emloft.net, johannes@...solutions.net, kuba@...nel.org,
        linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
        netdev@...r.kernel.org, pabeni@...hat.com,
        syzkaller-bugs@...glegroups.com
Subject: [syzbot] WARNING: suspicious RCU usage in ieee80211_tx_h_select_key

Hello,

syzbot found the following issue on:

HEAD commit:    ce522ba9ef7e Linux 5.18-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17b1ddc4f00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9ac56d6828346c4e
dashboard link: https://syzkaller.appspot.com/bug?extid=e550ebeb0bc610768394
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

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

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

=============================
WARNING: suspicious RCU usage
5.18.0-rc2-syzkaller #0 Not tainted
-----------------------------
net/mac80211/tx.c:604 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
3 locks held by kworker/u4:7/5407:
 #0: ffff888023e70938 ((wq_completion)phy24){+.+.}-{0:0}, at: process_one_work+0x796/0xd10 kernel/workqueue.c:2262
 #1: ffffc90002fffd00 ((work_completion)(&(&data->hw_scan)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0xd10 kernel/workqueue.c:2264
 #2: ffff88801c127128 (&data->mutex){+.+.}-{3:3}, at: hw_scan_work+0xbd/0xcf0 drivers/net/wireless/mac80211_hwsim.c:2431

stack backtrace:
CPU: 0 PID: 5407 Comm: kworker/u4:7 Not tainted 5.18.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy24 hw_scan_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 ieee80211_tx_h_select_key+0x6ba/0x14a0 net/mac80211/tx.c:604
 invoke_tx_handlers_early+0x9db/0x1cd0 net/mac80211/tx.c:1798
 invoke_tx_handlers net/mac80211/tx.c:1862 [inline]
 ieee80211_tx_prepare_skb+0x1c0/0x4d0 net/mac80211/tx.c:1885
 hw_scan_work+0x7e8/0xcf0 drivers/net/wireless/mac80211_hwsim.c:2478
 process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30
 </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.