[syzbot] [wpan?] WARNING in cfg802154_switch_netns

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: beb53f32698f Merge branch 'txgbe-irq_domain'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1559e64be80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc36d99546fe9035
dashboard link: https://syzkaller.appspot.com/bug?extid=6fbfe8fc7634822d0446
compiler: gcc (Debian 12.2.0-14) 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/131a55ff2911/disk-beb53f32.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/71ead9361bc3/vmlinux-beb53f32.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d210795a45c/bzImage-beb53f32.xz

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

RBP: 00007f1270356120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007f126f7abf80 R15: 00007ffe576000f8
</TASK>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 26030 at net/ieee802154/core.c:258 cfg802154_switch_netns+0x38b/0x450 net/ieee802154/core.c:258
Modules linked in:
CPU: 0 PID: 26030 Comm: syz-executor.1 Not tainted 6.8.0-rc1-syzkaller-00454-gbeb53f32698f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:cfg802154_switch_netns+0x38b/0x450 net/ieee802154/core.c:258
Code: df ff ff 48 8b 7b 20 e8 e3 69 3b fe 31 ff 89 c5 89 c6 e8 78 ac 47 f7 85 ed 0f 84 1f ff ff ff e9 11 ff ff ff e8 f6 b0 47 f7 90 <0f> 0b 90 e9 42 fe ff ff 4c 89 ef e8 25 d3 9f f7 e9 d3 fc ff ff e8
RSP: 0018:ffffc9000360f4f8 EFLAGS: 00010246
RAX: 0000000000040000 RBX: 00000000fffffff4 RCX: ffffc90010bf8000
RDX: 0000000000040000 RSI: ffffffff8a4072da RDI: 0000000000000005
RBP: ffff8880219a4198 R08: 0000000000000005 R09: 0000000000000000
R10: 00000000fffffff4 R11: 00000000001cf128 R12: 0000000000000000
R13: ffff88802adc9000 R14: ffff8880219a4078 R15: ffff8880219a4000
FS: 00007f12703566c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f29ebda8008 CR3: 000000007affe000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nl802154_wpan_phy_netns+0x134/0x2d0 net/ieee802154/nl802154.c:1292
genl_family_rcv_msg_doit+0x1fc/0x2e0 net/netlink/genetlink.c:1113
genl_family_rcv_msg net/netlink/genetlink.c:1193 [inline]
genl_rcv_msg+0x561/0x800 net/netlink/genetlink.c:1208
netlink_rcv_skb+0x16b/0x440 net/netlink/af_netlink.c:2543
genl_rcv+0x28/0x40 net/netlink/genetlink.c:1217
netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]
netlink_unicast+0x53b/0x810 net/netlink/af_netlink.c:1367
netlink_sendmsg+0x8b7/0xd70 net/netlink/af_netlink.c:1908
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0xd5/0x180 net/socket.c:745
____sys_sendmsg+0x6ac/0x940 net/socket.c:2584
___sys_sendmsg+0x135/0x1d0 net/socket.c:2638
__sys_sendmsg+0x117/0x1e0 net/socket.c:2667
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f126f67cda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f12703560c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f126f7abf80 RCX: 00007f126f67cda9
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007f1270356120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007f126f7abf80 R15: 00007ffe576000f8
</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