[syzbot] [wireless?] WARNING in ieee80211_link_info_change_notify (3)

[syzbot <syzbot+4b9a40c62f9a80195a4f@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    7e161a991ea7 Merge tag 'i2c-for-6.17-rc1-part2' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13f07aa2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a1bb6a60e53533c7
dashboard link: https://syzkaller.appspot.com/bug?extid=4b9a40c62f9a80195a4f
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 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/c830eae67136/disk-7e161a99.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cbc8fc9ead36/vmlinux-7e161a99.xz
kernel image: https://storage.googleapis.com/syzbot-assets/db1e8c2fe140/bzImage-7e161a99.xz

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

------------[ cut here ]------------
wlan1: Failed check-sdata-in-driver check, flags: 0x0
WARNING: CPU: 0 PID: 14825 at net/mac80211/main.c:425 ieee80211_link_info_change_notify+0x349/0x3f0 net/mac80211/main.c:425
Modules linked in:
CPU: 0 UID: 0 PID: 14825 Comm: syz.4.1907 Not tainted 6.16.0-syzkaller-11699-g7e161a991ea7 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ieee80211_link_info_change_notify+0x349/0x3f0 net/mac80211/main.c:425
Code: 74 24 08 48 81 c6 20 01 00 00 48 89 74 24 08 e8 fd f8 bc f6 8b 54 24 04 48 8b 74 24 08 48 c7 c7 c0 42 08 8d e8 48 97 7b f6 90 <0f> 0b 90 90 e9 0b fe ff ff e8 d9 f8 bc f6 90 0f 0b 90 e9 21 fd ff
RSP: 0018:ffffc90003c6fb30 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88805ab04d80 RCX: ffffc9000e0ef000
RDX: 0000000000080000 RSI: ffffffff817a3315 RDI: 0000000000000001
RBP: 0000000000040000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88805ab05728
R13: ffff88805ab06500 R14: 0000000000000000 R15: ffff88805abe8e40
FS:  00007fb6b366a6c0(0000) GS:ffff8881246c6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdb6ffb5f40 CR3: 000000005f61b000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ieee80211_recalc_txpower+0xe4/0x110 net/mac80211/iface.c:81
 ieee80211_set_tx_power+0x2b8/0x10d0 net/mac80211/cfg.c:3263
 rdev_set_tx_power net/wireless/rdev-ops.h:600 [inline]
 cfg80211_wext_siwtxpower+0x30e/0x680 net/wireless/wext-compat.c:893
 ioctl_standard_call+0xb5/0x1d0 net/wireless/wext-core.c:1043
 wireless_process_ioctl.constprop.0+0x291/0x3d0 net/wireless/wext-core.c:981
 wext_ioctl_dispatch net/wireless/wext-core.c:1014 [inline]
 wext_ioctl_dispatch net/wireless/wext-core.c:1002 [inline]
 wext_handle_ioctl+0x226/0x2a0 net/wireless/wext-core.c:1075
 sock_ioctl+0x3a1/0x6b0 net/socket.c:1291
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:598 [inline]
 __se_sys_ioctl fs/ioctl.c:584 [inline]
 __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb6b278eb69
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:00007fb6b366a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fb6b29b6080 RCX: 00007fb6b278eb69
RDX: 0000200000000040 RSI: 0000000000008b26 RDI: 0000000000000006
RBP: 00007fb6b2811df1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb6b29b6080 R15: 00007fffe088baf8
 </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 syzkaller@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