Hello, syzbot found the following issue on: HEAD commit: 2ba9f676d0a2 Merge tag 'drm-next-2024-11-29' of https://gi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13b7b9e8580000 kernel config: https://syzkaller.appspot.com/x/.config?x=7903df3280dd39ea dashboard link: https://syzkaller.appspot.com/bug?extid=bd5829ba3619f08e2341 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b7b9e8580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-2ba9f676.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/49a0011f6379/vmlinux-2ba9f676.xz kernel image: https://storage.googleapis.com/syzbot-assets/ac57640f6a59/bzImage-2ba9f676.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+bd5829ba3619f08e2341@xxxxxxxxxxxxxxxxxxxxxxxxx R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 R13: 0000000000000000 R14: 00007f2cedb45fa0 R15: 00007ffcd711e1d8 </TASK> ------------[ cut here ]------------ WARNING: CPU: 0 PID: 20692 at net/ieee802154/core.c:258 cfg802154_switch_netns+0x3c7/0x3d0 net/ieee802154/core.c:258 Modules linked in: CPU: 0 UID: 0 PID: 20692 Comm: syz.3.7229 Not tainted 6.12.0-syzkaller-11677-g2ba9f676d0a2 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:cfg802154_switch_netns+0x3c7/0x3d0 net/ieee802154/core.c:258 Code: e1 07 38 c1 7c 92 48 89 ef e8 c5 74 87 f6 eb 88 e8 7e 8d 1c f6 e9 66 fe ff ff e8 74 8d 1c f6 e9 5c fe ff ff e8 6a 8d 1c f6 90 <0f> 0b 90 e9 4e fe ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 RSP: 0018:ffffc9000dcff3c8 EFLAGS: 00010293 RAX: ffffffff8b795426 RBX: 00000000fffffff4 RCX: ffff888000342440 RDX: 0000000000000000 RSI: 00000000fffffff4 RDI: 0000000000000000 RBP: ffff88801f128198 R08: ffffffff8b795270 R09: 1ffffffff285fb12 R10: dffffc0000000000 R11: fffffbfff285fb13 R12: ffff888032cb4db0 R13: 0000000000000000 R14: ffff88801f128078 R15: dffffc0000000000 FS: 00007f2cee7af6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000120f6000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> nl802154_wpan_phy_netns+0x13d/0x210 net/ieee802154/nl802154.c:1292 genl_family_rcv_msg_doit net/netlink/genetlink.c:1115 [inline] genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0xb14/0xec0 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2542 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1321 [inline] netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1347 netlink_sendmsg+0x8e4/0xcb0 net/netlink/af_netlink.c:1891 sock_sendmsg_nosec net/socket.c:711 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:726 ____sys_sendmsg+0x52a/0x7e0 net/socket.c:2583 ___sys_sendmsg net/socket.c:2637 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2669 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:0x7f2ced980849 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:00007f2cee7af058 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f2cedb45fa0 RCX: 00007f2ced980849 RDX: 0000000000000000 RSI: 0000000020000f40 RDI: 0000000000000004 RBP: 00007f2cee7af0a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 R13: 0000000000000000 R14: 00007f2cedb45fa0 R15: 00007ffcd711e1d8 </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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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
