[v6.1] WARNING: still has locks held in cfg80211_wext_siwgenie

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a500ba24937a Linux 6.1.189
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=175787f5580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b386ef9cd0bf5977
dashboard link: https://syzkaller.appspot.com/bug?extid=21b87ecca544d5121c39
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11403725580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173a6ec9580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/61b37672b536/disk-a500ba24.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d21acd86f736/vmlinux-a500ba24.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a12c9b14ff99/Image-a500ba24.gz.xz

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

====================================
WARNING: syz.0.17/4463 still has locks held!
syzkaller #0 Not tainted
------------------------------------
1 lock held by syz.0.17/4463:
#0: ffff0000d0ef4d40 (&wdev->mtx){+.+.}-{3:3}, at: wdev_lock net/wireless/core.h:231 [inline]
#0: ffff0000d0ef4d40 (&wdev->mtx){+.+.}-{3:3}, at: cfg80211_wext_siwgenie+0xc8/0x370 net/wireless/wext-sme.c:340

stack backtrace:
CPU: 1 PID: 4463 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
print_held_locks_bug+0xb8/0x100 kernel/locking/lockdep.c:6648
debug_check_no_locks_held+0x5c/0x74 kernel/locking/lockdep.c:6654
do_exit+0x1114/0x19ac kernel/exit.c:909
do_group_exit+0x198/0x238 kernel/exit.c:1030
__do_sys_exit_group kernel/exit.c:1041 [inline]
__se_sys_exit_group kernel/exit.c:1039 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1039
__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/0x12c 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


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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