[v5.15] WARNING in restore_regulatory_settings (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12eef018180000
kernel config: https://syzkaller.appspot.com/x/.config?x=c170eb20d8be8542
dashboard link: https://syzkaller.appspot.com/bug?extid=d7c82f4d10613d91782e
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/528e8fe56997/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/18abf1e442f9/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0538a5d3b1f3/bzImage-6139f2a0.xz

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

------------[ cut here ]------------
Unexpected user alpha2: A�
WARNING: CPU: 1 PID: 29901 at net/wireless/reg.c:439 is_user_regdom_saved net/wireless/reg.c:437 [inline]
WARNING: CPU: 1 PID: 29901 at net/wireless/reg.c:439 restore_alpha2 net/wireless/reg.c:3372 [inline]
WARNING: CPU: 1 PID: 29901 at net/wireless/reg.c:439 restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Modules linked in:
CPU: 1 PID: 29901 Comm: kworker/1:25 Not tainted 5.15.148-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:437 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3372 [inline]
RIP: 0010:restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Code: 05 61 49 ef 07 88 44 24 1c e9 8e 01 00 00 e8 13 e9 f2 f7 41 0f be f6 0f be 15 48 49 ef 07 48 c7 c7 20 f8 91 8b e8 cc 9a be f7 <0f> 0b 4c 8b 35 d3 57 30 04 4d 85 f6 0f 84 85 00 00 00 4c 89 f0 48
RSP: 0018:ffffc90002dc7b40 EFLAGS: 00010246
RAX: 196ec03d18480700 RBX: 0000000000000000 RCX: ffff88807e07bb80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002dc7c48 R08: ffffffff81665d9c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88807d602a28 R14: 0000000000000041 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2da27000 CR3: 0000000023818000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
crda_timeout_work+0x23/0x50 net/wireless/reg.c:539
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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