[v6.6] WARNING in xfrm_state_fini

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cc1a1c5b404a Linux 6.6.103
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=131ca262580000
kernel config: https://syzkaller.appspot.com/x/.config?x=412020841cf033b0
dashboard link: https://syzkaller.appspot.com/bug?extid=71932961b7503c48bb75
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/46c06862a545/disk-cc1a1c5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/38ddabb6fc8b/vmlinux-cc1a1c5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b130b7d031b5/bzImage-cc1a1c5b.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 1073 at net/xfrm/xfrm_state.c:2997 xfrm_state_fini+0x25c/0x2b0 net/xfrm/xfrm_state.c:2997
Modules linked in:
CPU: 0 PID: 1073 Comm: kworker/u4:5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2025
Workqueue: netns cleanup_net
RIP: 0010:xfrm_state_fini+0x25c/0x2b0 net/xfrm/xfrm_state.c:2997
Code: 5c 41 5d 41 5e 41 5f 5d e9 81 20 00 00 e8 4c ed 66 f8 0f 0b e9 2c fe ff ff e8 40 ed 66 f8 0f 0b e9 91 fe ff ff e8 34 ed 66 f8 <0f> 0b 43 80 3c 2c 00 0f 85 fa fe ff ff e9 fd fe ff ff e8 1d ed 66
RSP: 0018:ffffc900047efa98 EFLAGS: 00010293
RAX: ffffffff891ea26c RBX: ffff88802f958000 RCX: ffff8880231ebc00
RDX: 0000000000000000 RSI: ffffffff8aaaba20 RDI: ffffffff8afc7040
RBP: 0000000000000040 R08: ffffffff90da550f R09: 1ffffffff21b4aa1
R10: dffffc0000000000 R11: fffffbfff21b4aa2 R12: 1ffff11005f2b274
R13: dffffc0000000000 R14: ffff88802f9593a0 R15: ffff88805fd5b200
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055de6c148950 CR3: 00000000686d2000 CR4: 00000000003506f0
Call Trace:
<TASK>
xfrm_net_exit+0x25/0x60 net/xfrm/xfrm_policy.c:4276
ops_exit_list net/core/net_namespace.c:173 [inline]
cleanup_net+0x6f4/0xb90 net/core/net_namespace.c:652
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.