From: Kees Cook <kees@kernel.org>
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot <syzbot+4bcdddd48bb6f0be0da1@syzkaller.appspotmail.com>,
johannes@sipsolutions.net, 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 ieee80211_request_ibss_scan
Date: Fri, 9 May 2025 11:35:01 -0700 [thread overview]
Message-ID: <202505091124.40FF7F9B1@keescook> (raw)
In-Reply-To: <680fd171.050a0220.2b69d1.045e.GAE@google.com>
On Mon, Apr 28, 2025 at 12:05:21PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 5bc1018675ec Merge tag 'pci-v6.15-fixes-3' of git://git.ke..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17ca0374580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=90837c100b88a636
> dashboard link: https://syzkaller.appspot.com/bug?extid=4bcdddd48bb6f0be0da1
> compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a39d74580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106fa270580000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-5bc10186.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/3a2f39285e07/vmlinux-5bc10186.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/2a37a55f34fb/bzImage-5bc10186.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/cc5918853785/mount_4.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+4bcdddd48bb6f0be0da1@syzkaller.appspotmail.com
>
> wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
> wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
> wlan1: Trigger new scan to find an IBSS to join
> ------------[ cut here ]------------
> UBSAN: array-index-out-of-bounds in net/mac80211/scan.c:1208:5
> index 0 is out of range for type 'struct ieee80211_channel *[] __counted_by(n_channels)' (aka 'struct ieee80211_channel *[]')
> CPU: 0 UID: 0 PID: 131 Comm: kworker/u4:5 Not tainted 6.15.0-rc3-syzkaller-00342-g5bc1018675ec #0 PREEMPT(full)
> 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
> Call Trace:
> <TASK>
> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
> ubsan_epilogue+0xa/0x40 lib/ubsan.c:231
> __ubsan_handle_out_of_bounds+0xe9/0xf0 lib/ubsan.c:453
> ieee80211_request_ibss_scan+0x600/0x8b0 net/mac80211/scan.c:1208
This looks like another case of using the array before specifying the
valid entries:
...
local->int_scan_req->channels[n_ch] = tmp_ch;
n_ch++;
}
}
...
local->int_scan_req->n_channels = n_ch;
n_channels controls what array array entries are valid.
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-05-09 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 19:05 [syzbot] [wireless?] UBSAN: array-index-out-of-bounds in ieee80211_request_ibss_scan syzbot
2025-05-09 18:35 ` Kees Cook [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=202505091124.40FF7F9B1@keescook \
--to=kees@kernel.org \
--cc=eadavis@qq.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+4bcdddd48bb6f0be0da1@syzkaller.appspotmail.com \
--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).