Hello,
syzbot found the following issue on:
HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=101f96f9580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link:
https://syzkaller.appspot.com/bug?extid=f007ee81bb3dd463adaf
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.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/425a730ba33a/disk-cf82dcca.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/7dd95cb647d8/vmlinux-cf82dcca.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/1b21aedea13f/Image-cf82dcca.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f007ee...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8634 at net/mac80211/iface.c:532 ieee80211_do_stop+0xb2c/0x1ba0 net/mac80211/iface.c:532
Modules linked in:
CPU: 0 PID: 8634 Comm: syz.3.1093 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/07/2026
pstate: 62400005 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : ieee80211_do_stop+0xb2c/0x1ba0 net/mac80211/iface.c:532
lr : ieee80211_do_stop+0xb2c/0x1ba0 net/mac80211/iface.c:532
sp : ffff8000215574c0
x29: ffff800021557690 x28: dfff800000000000 x27: ffff0000c6568e80
x26: dfff800000000000 x25: ffff0000f4f78000 x24: 0000000000000007
x23: ffff800021557580 x22: ffff0000f4f7a760 x21: 0000000000000001
x20: ffff7000042aaeac x19: ffff0000f4f78c80 x18: 1fffe00033e6df7e
x17: ffff80001539d000 x16: ffff800011ba0e90 x15: ffff8000089b6798
x14: 0000000000000001 x13: 1ffff000042aae60 x12: 0000000000080000
x11: 000000000007ffff x10: ffff8000297af000 x9 : ffff8000113f8ac8
x8 : 0000000000080000 x7 : ffff80000805a700 x6 : ffff80000805a910
x5 : ffff0001016efec0 x4 : ffff800021557008 x3 : ffff800011c77390
x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
ieee80211_do_stop+0xb2c/0x1ba0 net/mac80211/iface.c:532
ieee80211_stop+0x398/0x400 net/mac80211/iface.c:815
__dev_close_many+0x2ac/0x3a0 net/core/dev.c:1585
dev_close_many+0x1e8/0x448 net/core/dev.c:1610
dev_close+0x150/0x208 net/core/dev.c:1636
cfg80211_shutdown_all_interfaces+0xb8/0x1c8 net/wireless/core.c:275
cfg80211_rfkill_set_block+0x30/0x50 net/wireless/core.c:307
rfkill_set_block+0x194/0x33c net/rfkill/core.c:360
rfkill_fop_write+0x488/0x5ac net/rfkill/core.c:1318
vfs_write+0x2a8/0x7c8 fs/read_write.c:582
ksys_write+0x12c/0x228 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 5512
hardirqs last enabled at (5511): [<ffff8000088f6370>] kasan_quarantine_put+0xc4/0x200 mm/kasan/quarantine.c:242
hardirqs last disabled at (5512): [<ffff800011b9d0cc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (5472): [<ffff80001156bc6c>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (5472): [<ffff80001156bc6c>] mesh_path_flush_by_nexthop+0x108/0x124 net/mac80211/mesh_pathtbl.c:552
softirqs last disabled at (5470): [<ffff80001156bbb8>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (5470): [<ffff80001156bbb8>] mesh_path_flush_by_nexthop+0x54/0x124 net/mac80211/mesh_pathtbl.c:547
---[ 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
syzk...@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