[v5.15] WARNING in ieee80211_free_keys

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3b8db0e4f263 Linux 5.15.182
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114f2cf4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=dd5e00a2e31fafd7
dashboard link: https://syzkaller.appspot.com/bug?extid=9cceb645b9dc1bd65454
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ff1afedf7b4d/disk-3b8db0e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19cb045784cf/vmlinux-3b8db0e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/43c663d2f6a5/Image-3b8db0e4.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9cceb6...@syzkaller.appspotmail.com

netdevsim netdevsim3 netdevsim2: unset [1, 0] type 2 family 0 port 6081 - 0
netdevsim netdevsim3 netdevsim3: unset [1, 0] type 2 family 0 port 6081 - 0
tipc: Resetting bearer <eth:syzkaller0>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7146 at net/mac80211/key.c:1064 ieee80211_free_keys+0x62c/0x704 net/mac80211/key.c:1063
Modules linked in:
CPU: 0 PID: 7146 Comm: syz.3.898 Not tainted 5.15.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ieee80211_free_keys+0x62c/0x704 net/mac80211/key.c:1063
lr : ieee80211_free_keys+0x62c/0x704 net/mac80211/key.c:1063
sp : ffff80001f946060
x29: ffff80001f946100 x28: 0000000000001b30 x27: dfff800000000000
x26: ffff0000d0cc8dc0 x25: 1ffff00003f28c14 x24: ffff80001f9460c0
x23: ffff0000e9bd6298 x22: 0000000000000001 x21: 0000000000000002
x20: ffff0000e9bd4c80 x19: ffff0000e9bd4c80 x18: 0000000000000002
x17: 0000000000000040 x16: ffff8000111a53fc x15: 0000000000000000
x14: 0000000000000040 x13: 1ffff0000282a06b x12: 0000000000080000
x11: 000000000007ffff x10: ffff800023cd9000 x9 : ffff800010b7be60
x8 : 0000000000080000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80001126f084
x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000002
Call trace:
ieee80211_free_keys+0x62c/0x704 net/mac80211/key.c:1063
ieee80211_do_stop+0xb94/0x1898 net/mac80211/iface.c:508
ieee80211_stop+0x134/0x190 net/mac80211/iface.c:667
__dev_close_many+0x2b8/0x3a8 net/core/dev.c:1621
dev_close_many+0x1e8/0x440 net/core/dev.c:1646
dev_close+0x148/0x1f8 net/core/dev.c:1672
ieee80211_stop+0xd0/0x190 net/mac80211/iface.c:663
__dev_close_many+0x2b8/0x3a8 net/core/dev.c:1621
__dev_close net/core/dev.c:1633 [inline]
__dev_change_flags+0x3e8/0x54c net/core/dev.c:8851
dev_change_flags+0x80/0x154 net/core/dev.c:8924
do_setlink+0xa20/0x3088 net/core/rtnetlink.c:2779
rtnl_group_changelink net/core/rtnetlink.c:3296 [inline]
__rtnl_newlink net/core/rtnetlink.c:3460 [inline]
rtnl_newlink+0xb98/0x1404 net/core/rtnetlink.c:3572
rtnetlink_rcv_msg+0x9d4/0xd04 net/core/rtnetlink.c:5650
netlink_rcv_skb+0x208/0x3c4 net/netlink/af_netlink.c:2489
rtnetlink_rcv+0x28/0x38 net/core/rtnetlink.c:5668
netlink_unicast_kernel net/netlink/af_netlink.c:1311 [inline]
netlink_unicast+0x60c/0x89c net/netlink/af_netlink.c:1337
netlink_sendmsg+0x6e8/0x9cc net/netlink/af_netlink.c:1905
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
____sys_sendmsg+0x61c/0x920 net/socket.c:2436
___sys_sendmsg+0x1d0/0x240 net/socket.c:2490
__sys_sendmsg net/socket.c:2519 [inline]
__do_sys_sendmsg net/socket.c:2528 [inline]
__se_sys_sendmsg net/socket.c:2526 [inline]
__arm64_sys_sendmsg+0x1a8/0x254 net/socket.c:2526
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 100450
hardirqs last enabled at (100449): [<ffff80001127f064>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last enabled at (100449): [<ffff80001127f064>] _raw_spin_unlock_irqrestore+0xa8/0x14c kernel/locking/spinlock.c:194
hardirqs last disabled at (100450): [<ffff8000111a0cd0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (100418): [<ffff800010afaa90>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (100418): [<ffff800010afaa90>] netif_addr_unlock_bh include/linux/netdevice.h:4625 [inline]
softirqs last enabled at (100418): [<ffff800010afaa90>] ieee80211_do_stop+0x4c4/0x1898 net/mac80211/iface.c:445
softirqs last disabled at (100414): [<ffff800010afdfd8>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace d55862650ac73479 ]---
device syzkaller0 left promiscuous mode


---
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.