[v6.1] WARNING: lock held when returning to user space in nl80211_set_cqm

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6c6a6c7e211c Linux 6.1.66
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1440466ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8fa519fe1c08a54
dashboard link: https://syzkaller.appspot.com/bug?extid=c5aa1f439e15d4ece58b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eac1cb0e5463/disk-6c6a6c7e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1db219b6fef3/vmlinux-6c6a6c7e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6002cd716be7/bzImage-6c6a6c7e.xz

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

netlink: 4 bytes leftover after parsing attributes in process `syz-executor.0'.
================================================
WARNING: lock held when returning to user space!
6.1.66-syzkaller #0 Not tainted
------------------------------------------------
syz-executor.0/14878 is leaving the kernel with locks still held!
1 lock held by syz-executor.0/14878:
#0: ffff888047c74d40 (&wdev->mtx){+.+.}-{3:3}, at: wdev_lock net/wireless/core.h:231 [inline]
#0: ffff888047c74d40 (&wdev->mtx){+.+.}-{3:3}, at: nl80211_set_cqm_rssi net/wireless/nl80211.c:12654 [inline]
#0: ffff888047c74d40 (&wdev->mtx){+.+.}-{3:3}, at: nl80211_set_cqm+0x6da/0x1110 net/wireless/nl80211.c:12744


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