From: syzbot <syzbot+fd222bb38e916df26fa4@syzkaller.appspotmail.com>
To: johannes.berg@intel.com, johannes@sipsolutions.net,
lachlan.hodges@morsemicro.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] UBSAN: array-index-out-of-bounds in cfg80211_inform_bss_frame_data
Date: Fri, 13 Jun 2025 14:30:02 -0700 [thread overview]
Message-ID: <684c985a.050a0220.be214.02a7.GAE@google.com> (raw)
In-Reply-To: <684b6ff9.a00a0220.279073.0007.GAE@google.com>
syzbot has bisected this issue to:
commit 1e1f706fc2ce90eaaf3480b3d5f27885960d751c
Author: Lachlan Hodges <lachlan.hodges@morsemicro.com>
Date: Tue Jun 3 05:35:38 2025 +0000
wifi: cfg80211/mac80211: correctly parse S1G beacon optional elements
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10f60e82580000
start commit: d9816ec74e6d macsec: MACsec SCI assignment for ES = 0
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=12f60e82580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14f60e82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=73696606574e3967
dashboard link: https://syzkaller.appspot.com/bug?extid=fd222bb38e916df26fa4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1042460c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1442460c580000
Reported-by: syzbot+fd222bb38e916df26fa4@syzkaller.appspotmail.com
Fixes: 1e1f706fc2ce ("wifi: cfg80211/mac80211: correctly parse S1G beacon optional elements")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-13 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 0:25 [syzbot] [wireless?] UBSAN: array-index-out-of-bounds in cfg80211_inform_bss_frame_data syzbot
2025-06-13 21:30 ` syzbot [this message]
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=684c985a.050a0220.be214.02a7.GAE@google.com \
--to=syzbot+fd222bb38e916df26fa4@syzkaller.appspotmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=lachlan.hodges@morsemicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).