[syzbot] [net?] WARNING in rtnl_dellink (4)

[syzbot <syzbot+e1153ace01ff073581b7@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    6d858708d465 Merge branch 'net-ethernet-freescale-use-pa-t..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15ce50a7980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e7f0cac6eaefe81d
dashboard link: https://syzkaller.appspot.com/bug?extid=e1153ace01ff073581b7
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/88c678a36ec8/disk-6d858708.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b19b4fbbd593/vmlinux-6d858708.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18fef9c3fe20/bzImage-6d858708.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 31309 at net/core/dev.c:9526 dev_xdp_uninstall net/core/dev.c:9526 [inline]
WARNING: CPU: 1 PID: 31309 at net/core/dev.c:9526 unregister_netdevice_many_notify+0x18c8/0x1da0 net/core/dev.c:11468
Modules linked in:
CPU: 1 UID: 0 PID: 31309 Comm: syz.4.12366 Not tainted 6.12.0-rc2-syzkaller-00631-g6d858708d465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:dev_xdp_uninstall net/core/dev.c:9526 [inline]
RIP: 0010:unregister_netdevice_many_notify+0x18c8/0x1da0 net/core/dev.c:11468
Code: 00 f8 90 0f 0b 90 e9 4f ff ff ff e8 42 25 00 f8 90 0f 0b 90 eb 9d e8 37 25 00 f8 90 0f 0b 90 e9 e8 f1 ff ff e8 29 25 00 f8 90 <0f> 0b 90 e9 5a f3 ff ff e8 1b 25 00 f8 90 0f 0b 90 e9 cd f4 ff ff
RSP: 0018:ffffc9000efd6fc0 EFLAGS: 00010283
RAX: ffffffff8994c227 RBX: 00000000ffffffa1 RCX: 0000000000040000
RDX: ffffc9000a0a1000 RSI: 0000000000000dad RDI: 0000000000000dae
RBP: ffffc9000efd71b0 R08: ffffffff8994b57d R09: ffffffff8667d4c8
R10: 0000000000000004 R11: ffff8880619cda00 R12: ffffc90004cdd000
R13: 1ffff1100f056986 R14: ffff8880782b4c30 R15: ffff8880782b4c28
FS:  00007fe4187436c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5ea6d0cfce CR3: 0000000027e0a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rtnl_delete_link net/core/rtnetlink.c:3355 [inline]
 rtnl_dellink+0x50b/0x8d0 net/core/rtnetlink.c:3407
 rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6749
 netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2551
 netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline]
 netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1357
 netlink_sendmsg+0x8e4/0xcb0 net/netlink/af_netlink.c:1901
 sock_sendmsg_nosec net/socket.c:729 [inline]
 __sock_sendmsg+0x221/0x270 net/socket.c:744
 ____sys_sendmsg+0x52a/0x7e0 net/socket.c:2607
 ___sys_sendmsg net/socket.c:2661 [inline]
 __sys_sendmsg+0x292/0x380 net/socket.c:2690
 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:0x7fe41797dff9
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:00007fe418743038 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fe417b35f80 RCX: 00007fe41797dff9
RDX: 0000000020004010 RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00007fe4179f0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fe417b35f80 R15: 00007ffd07629398
 </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