[syzbot] [netfilter?] WARNING in nf_hook_entry_head

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

Hello,

syzbot found the following issue on:

HEAD commit:    052d534373b7 Merge tag 'exfat-for-6.8-rc1' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=111ec0fbe80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7c8840a4a09eab8
dashboard link: https://syzkaller.appspot.com/bug?extid=ea8f0147cde55bfa62e9
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-052d5343.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a58a0f0eb33d/vmlinux-052d5343.xz
kernel image: https://storage.googleapis.com/syzbot-assets/019e6b0bba7a/bzImage-052d5343.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4052 at net/netfilter/core.c:302 nf_hook_entry_head+0x289/0x300 net/netfilter/core.c:302
Modules linked in:
CPU: 1 PID: 4052 Comm: kworker/u16:32 Not tainted 6.7.0-syzkaller-09928-g052d534373b7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: netns cleanup_net
RIP: 0010:nf_hook_entry_head+0x289/0x300 net/netfilter/core.c:302
Code: 80 3c 02 00 0f 85 82 00 00 00 4d 3b a5 08 01 00 00 75 a0 e8 c9 c0 cf f8 49 81 c5 90 00 00 00 e9 ae fe ff ff e8 b8 c0 cf f8 90 <0f> 0b 90 e9 24 ff ff ff e8 aa c0 cf f8 90 0f 0b 90 e9 16 ff ff ff
RSP: 0018:ffffc9000c417ac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff88b736e5
RDX: ffff88803a6c2400 RSI: ffffffff88b73898 RDI: ffff888029572108
RBP: 0000000000000005 R08: 0000000000000005 R09: 0000000000000005
R10: 0000000000000005 R11: ffffffff8ace21e0 R12: ffff888064b59cc0
R13: ffff888029572000 R14: ffff88810a331c28 R15: ffff888035da3dec
FS:  0000000000000000(0000) GS:ffff88806b700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005569f03ef238 CR3: 000000002d4cc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __nf_unregister_net_hook+0x81/0x680 net/netfilter/core.c:494
 nf_unregister_net_hook net/netfilter/core.c:533 [inline]
 nf_unregister_net_hook+0xf3/0x110 net/netfilter/core.c:529
 nft_netdev_unregister_hooks+0xaf/0x270 net/netfilter/nf_tables_api.c:309
 __nf_tables_unregister_hook net/netfilter/nf_tables_api.c:358 [inline]
 __nf_tables_unregister_hook net/netfilter/nf_tables_api.c:340 [inline]
 __nft_release_hook+0x446/0x560 net/netfilter/nf_tables_api.c:11218
 __nft_release_hooks net/netfilter/nf_tables_api.c:11233 [inline]
 nf_tables_pre_exit_net+0xc5/0x120 net/netfilter/nf_tables_api.c:11379
 ops_pre_exit_list net/core/net_namespace.c:160 [inline]
 cleanup_net+0x46c/0xb20 net/core/net_namespace.c:606
 process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
 process_scheduled_works kernel/workqueue.c:2706 [inline]
 worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
 kthread+0x2c6/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
 </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