From: syzbot <syzbot+e785ad5c3cc8ca31eeac@syzkaller.appspotmail.com>
To: johannes@sipsolutions.net, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] WARNING in _ieee80211_change_chanctx (2)
Date: Mon, 10 Nov 2025 14:00:30 -0800 [thread overview]
Message-ID: <6912607e.a70a0220.22f260.010f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: dcb6fa37fd7b Linux 6.18-rc3
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=14e07812580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=e785ad5c3cc8ca31eeac
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ae6bec0d0398/disk-dcb6fa37.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dcc732da66c3/vmlinux-dcb6fa37.xz
kernel image: https://storage.googleapis.com/syzbot-assets/301d1bbdecc2/Image-dcb6fa37.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e785ad5c3cc8ca31eeac@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 17489 at net/mac80211/chan.c:544 _ieee80211_change_chanctx+0x25c/0x10f4 net/mac80211/chan.c:544
Modules linked in:
CPU: 0 UID: 0 PID: 17489 Comm: syz.1.3194 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : _ieee80211_change_chanctx+0x25c/0x10f4 net/mac80211/chan.c:544
lr : _ieee80211_change_chanctx+0x25c/0x10f4 net/mac80211/chan.c:544
sp : ffff8000991c67c0
x29: ffff8000991c68e0 x28: 0000000000000006 x27: dfff800000000000
x26: 0000000000000006 x25: ffff0000f6909800 x24: ffff8000991c69c0
x23: ffff0000f69098b0 x22: ffff0000d52b3398 x21: 0000000000000000
x20: ffff0000f6909800 x19: ffff0000d52b0e80 x18: 0000000000000000
x17: 0000000000000000 x16: ffff80008052a444 x15: 0000000000000005
x14: 0000000000000002 x13: 000000000000000d x12: 0000000000ff0100
x11: 0000000000080000 x10: 0000000000003423 x9 : ffff8000a5ddb000
x8 : 0000000000003424 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff8000991c6a10 x4 : 0000000000000000 x3 : ffff8000991c69c0
x2 : ffff0000f6909800 x1 : ffff800092ae0f10 x0 : 0000000000000006
Call trace:
_ieee80211_change_chanctx+0x25c/0x10f4 net/mac80211/chan.c:544 (P)
ieee80211_change_chanctx net/mac80211/chan.c:590 [inline]
ieee80211_recalc_chanctx_chantype+0xcec/0xdf4 net/mac80211/chan.c:865
ieee80211_vif_use_reserved_switch+0x1470/0x22b0 net/mac80211/chan.c:1763
ieee80211_link_use_reserved_context+0x2e8/0x4ec net/mac80211/chan.c:2017
__ieee80211_csa_finalize net/mac80211/cfg.c:4114 [inline]
ieee80211_csa_finalize+0x464/0xf08 net/mac80211/cfg.c:4145
__ieee80211_channel_switch net/mac80211/cfg.c:4424 [inline]
ieee80211_channel_switch+0x834/0xa40 net/mac80211/cfg.c:4439
rdev_channel_switch+0x124/0x300 net/wireless/rdev-ops.h:1116
nl80211_channel_switch+0x8d8/0xb18 net/wireless/nl80211.c:11476
genl_family_rcv_msg_doit+0x1d8/0x2bc net/netlink/genetlink.c:1115
genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]
genl_rcv_msg+0x450/0x624 net/netlink/genetlink.c:1210
netlink_rcv_skb+0x220/0x3fc net/netlink/af_netlink.c:2552
genl_rcv+0x38/0x50 net/netlink/genetlink.c:1219
netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
netlink_unicast+0x694/0x8c4 net/netlink/af_netlink.c:1346
netlink_sendmsg+0x648/0x930 net/netlink/af_netlink.c:1896
sock_sendmsg_nosec net/socket.c:727 [inline]
__sock_sendmsg net/socket.c:742 [inline]
____sys_sendmsg+0x490/0x7b8 net/socket.c:2630
___sys_sendmsg+0x204/0x278 net/socket.c:2684
__sys_sendmsg net/socket.c:2716 [inline]
__do_sys_sendmsg net/socket.c:2721 [inline]
__se_sys_sendmsg net/socket.c:2719 [inline]
__arm64_sys_sendmsg+0x184/0x238 net/socket.c:2719
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:746
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
irq event stamp: 772
hardirqs last enabled at (771): [<ffff800080c84b38>] kasan_quarantine_put+0x1a0/0x1c8 mm/kasan/quarantine.c:234
hardirqs last disabled at (772): [<ffff80008adecb80>] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:434
softirqs last enabled at (732): [<ffff8000803d8488>] softirq_handle_end kernel/softirq.c:468 [inline]
softirqs last enabled at (732): [<ffff8000803d8488>] handle_softirqs+0xaf8/0xc88 kernel/softirq.c:650
softirqs last disabled at (693): [<ffff800080022024>] __do_softirq+0x14/0x20 kernel/softirq.c:656
---[ end trace 0000000000000000 ]---
---
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.
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
reply other threads:[~2025-11-10 22:00 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=6912607e.a70a0220.22f260.010f.GAE@google.com \
--to=syzbot+e785ad5c3cc8ca31eeac@syzkaller.appspotmail.com \
--cc=johannes@sipsolutions.net \
--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.