From: syzbot <syzbot+list297c04812c0701bce1d8@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly wireless report (Sep 2026)
Date: Fri, 04 Sep 2026 05:33:29 -0700 [thread overview]
Message-ID: <6a9aba99.efa90033.8a9e.0004.GAE@google.com> (raw)
Hello wireless maintainers/developers,
This is a 31-day syzbot report for the wireless subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/wireless
During the period, 1 new issues were detected and 0 were fixed.
In total, 28 issues are still open and 183 have already been fixed.
There are also 22 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6988 Yes WARNING in __cfg80211_ibss_joined (2)
https://syzkaller.appspot.com/bug?extid=7f064ba1704c2466e36d
<2> 1394 Yes INFO: task hung in reg_process_self_managed_hints
https://syzkaller.appspot.com/bug?extid=1f16507d9ec05f64210a
<3> 732 Yes INFO: task hung in crda_timeout_work (8)
https://syzkaller.appspot.com/bug?extid=d41f74db64598e0b5016
<4> 355 Yes INFO: task hung in ath9k_hif_usb_firmware_cb (3)
https://syzkaller.appspot.com/bug?extid=e9b1ff41aa6a7ebf9640
<5> 102 Yes WARNING in cfg80211_scan_done
https://syzkaller.appspot.com/bug?extid=189dcafc06865d38178d
<6> 51 Yes WARNING: ODEBUG bug in ieee80211_led_exit (2)
https://syzkaller.appspot.com/bug?extid=e84ecca6d1fa09a9b3d9
<7> 44 Yes INFO: task hung in nl80211_pre_doit (3)
https://syzkaller.appspot.com/bug?extid=da14e8c0ada830335981
<8> 20 Yes WARNING in __cfg80211_bss_update (2)
https://syzkaller.appspot.com/bug?extid=1a797e1c81be78a2ace7
<9> 16 Yes INFO: task hung in cfg80211_event_work (4)
https://syzkaller.appspot.com/bug?extid=5506b2556159a1ab6923
<10> 6 Yes WARNING in __carl9170_tx_process_status
https://syzkaller.appspot.com/bug?extid=381102a7292a374fe8a7
---
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.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-09-04 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a9aba99.efa90033.8a9e.0004.GAE@google.com \
--to=syzbot+list297c04812c0701bce1d8@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.