[v6.6] WARNING in ieee80211_free_keys

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5bbb12db2c7 Linux 6.6.115
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=141db932580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=41edbe8e08e6d026c1c8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e6860876f0ec/disk-e5bbb12d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d6c28d7cc7f3/vmlinux-e5bbb12d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f52ba3964b2/bzImage-e5bbb12d.xz

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

tipc: Resetting bearer <eth:syzkaller0>
------------[ cut here ]------------
WARNING: CPU: 1 PID: 10909 at net/mac80211/key.c:1165 ieee80211_free_keys+0x4c0/0x5b0 net/mac80211/key.c:1164
Modules linked in:
CPU: 1 PID: 10909 Comm: syz.1.1176 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ieee80211_free_keys+0x4c0/0x5b0 net/mac80211/key.c:1164
Code: 00 00 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 80 00 00 00 75 7f 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b0 42 95 f7 <0f> 0b e9 44 fe ff ff e8 a4 42 95 f7 e9 31 fe ff ff 44 89 f1 80 e1
RSP: 0018:ffffc900042376a0 EFLAGS: 00010283
RAX: ffffffff89f04ce0 RBX: dffffc0000000000 RCX: 0000000000080000
RDX: ffffc9000d4fa000 RSI: 00000000000058b4 RDI: 00000000000058b5
RBP: ffffc90004237770 R08: ffffffff90da85f7 R09: 1ffffffff21b50be
R10: dffffc0000000000 R11: fffffbfff21b50bf R12: 0000000000000001
R13: ffff88805dd10c80 R14: 0000000000000002 R15: ffff8880775d29e8
FS: 00007fcb60fde6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000028196000 CR4: 00000000003506e0
DR0: 0000000000000004 DR1: 000000000000e613 DR2: 0000100000000403
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_do_stop+0xec8/0x1db0 net/mac80211/iface.c:605
ieee80211_stop+0x436/0x4a0 net/mac80211/iface.c:795
__dev_close_many+0x1c3/0x2a0 net/core/dev.c:1590
__dev_close net/core/dev.c:1602 [inline]
__dev_change_flags+0x2c4/0x6a0 net/core/dev.c:8683
dev_change_flags+0x88/0x1a0 net/core/dev.c:8757
dev_ifsioc+0x6a7/0xe20 net/core/dev_ioctl.c:529
dev_ioctl+0x7e2/0x1170 net/core/dev_ioctl.c:786
sock_do_ioctl+0x226/0x2f0 net/socket.c:1236
sock_ioctl+0x623/0x7a0 net/socket.c:1341
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcb6018efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcb60fde038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fcb603e5fa0 RCX: 00007fcb6018efc9
RDX: 0000200000000080 RSI: 0000000000008914 RDI: 0000000000000004
RBP: 00007fcb60211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcb603e6038 R14: 00007fcb603e5fa0 R15: 00007ffd909a76f8
</TASK>


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