Hello, syzbot found the following issue on: HEAD commit: ccb35037c48a Merge branch 'net-lan969x-add-vcap-functional.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=1492cf40580000 kernel config: https://syzkaller.appspot.com/x/.config?x=a9d1c42858837b59 dashboard link: https://syzkaller.appspot.com/bug?extid=9ea265d998de25ac6a46 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/4c339ec95c42/disk-ccb35037.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/328f6f24277e/vmlinux-ccb35037.xz kernel image: https://storage.googleapis.com/syzbot-assets/0473d4109fcb/bzImage-ccb35037.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+9ea265d998de25ac6a46@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 16303 at drivers/net/wireless/virtual/mac80211_hwsim.c:1445 mac80211_hwsim_config_mac_nl+0x2b2/0x370 drivers/net/wireless/virtual/mac80211_hwsim.c:1445 Modules linked in: CPU: 0 UID: 0 PID: 16303 Comm: syz.6.3042 Not tainted 6.12.0-rc5-syzkaller-01164-gccb35037c48a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 RIP: 0010:mac80211_hwsim_config_mac_nl+0x2b2/0x370 drivers/net/wireless/virtual/mac80211_hwsim.c:1445 Code: 48 8b 3c 24 4c 89 fe 44 89 ea 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 eb f8 ff ff e8 46 b3 8d fa eb 05 e8 3f b3 8d fa 90 <0f> 0b 90 e9 10 fe ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 90 fd RSP: 0018:ffffc9000b0476b0 EFLAGS: 00010293 RAX: ffffffff870726e1 RBX: 0000000000000000 RCX: ffff888072945a00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: ffffffff870724ed R09: 1ffffffff203a5d5 R10: dffffc0000000000 R11: ffffffff87069560 R12: ffff8880635dae32 R13: 0000000000000000 R14: 0000000000000001 R15: ffff8880554630a0 FS: 00007f08d2bff6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020003a80 CR3: 000000007c7cc000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> mac80211_hwsim_add_interface+0x9a/0x320 drivers/net/wireless/virtual/mac80211_hwsim.c:2136 drv_add_interface+0x2f8/0x8e0 net/mac80211/driver-ops.c:73 ieee80211_do_open+0x73d/0x2430 net/mac80211/iface.c:1373 ieee80211_open+0x192/0x200 net/mac80211/iface.c:458 __dev_open+0x2d3/0x450 net/core/dev.c:1476 __dev_change_flags+0x1e2/0x6f0 net/core/dev.c:8904 dev_change_flags+0x8b/0x1a0 net/core/dev.c:8976 devinet_ioctl+0xcce/0x1ac0 net/ipv4/devinet.c:1209 inet_ioctl+0x3d7/0x4f0 net/ipv4/af_inet.c:1001 sock_do_ioctl+0x158/0x460 net/socket.c:1227 sock_ioctl+0x626/0x8e0 net/socket.c:1346 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f08d317e31b Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 RSP: 002b:00007f08d2bfde60 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f08d2bfdf80 RCX: 00007f08d317e31b RDX: 00007f08d2bfdee0 RSI: 0000000000008914 RDI: 000000000000000b RBP: 000000000000000b R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000024 R13: 0000000000000048 R14: 00007f08d2bfdfa0 R15: 00007f08d2bfdee0 </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@xxxxxxxxxxxxxxxx. 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