[v6.1] WARNING in restore_regulatory_settings

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 883d1a956208 Linux 6.1.75
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170d1a88180000
kernel config: https://syzkaller.appspot.com/x/.config?x=eccd04e6e3c1192
dashboard link: https://syzkaller.appspot.com/bug?extid=f5bd1fa6c3d2badb3dc1
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/5edd2ddd12db/disk-883d1a95.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f400bf7c3ec/vmlinux-883d1a95.xz
kernel image: https://storage.googleapis.com/syzbot-assets/74db8d43a4af/bzImage-883d1a95.xz

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

------------[ cut here ]------------
Unexpected user alpha2: A�
WARNING: CPU: 0 PID: 3622 at net/wireless/reg.c:440 is_user_regdom_saved net/wireless/reg.c:438 [inline]
WARNING: CPU: 0 PID: 3622 at net/wireless/reg.c:440 restore_alpha2 net/wireless/reg.c:3432 [inline]
WARNING: CPU: 0 PID: 3622 at net/wireless/reg.c:440 restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3524
Modules linked in:
CPU: 0 PID: 3622 Comm: kworker/0:3 Not tainted 6.1.75-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events_power_efficient crda_timeout_work
RIP: 0010:is_user_regdom_saved net/wireless/reg.c:438 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3432 [inline]
RIP: 0010:restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3524
Code: 05 61 4b 27 08 88 44 24 1c e9 8e 01 00 00 e8 f3 05 a3 f7 41 0f be f6 0f be 15 48 4b 27 08 48 c7 c7 c0 0d fb 8b e8 3c 07 6b f7 <0f> 0b 4c 8b 35 d3 23 63 04 4d 85 f6 0f 84 85 00 00 00 4c 89 f0 48
RSP: 0018:ffffc900055ffb40 EFLAGS: 00010246
RAX: 19d368f0d2999f00 RBX: 0000000000000000 RCX: ffff888015b88000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900055ffc48 R08: ffffffff8152770e R09: fffff52000abfec9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100494e3c3 R14: 0000000000000041 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff4ee1a8000 CR3: 0000000039d49000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
crda_timeout_work+0x23/0x50 net/wireless/reg.c:540
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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