[syzbot] [netfilter?] WARNING: suspicious RCU usage in expect_iter_name
From: syzbot <hidden>
Date: 2026-09-12 00:57:28
Also in:
lkml, netfilter-devel
Hello, syzbot found the following issue on: HEAD commit: 15071f2a1263 Merge branch 'bpf-tcp-fix-bpf_sock_destroy-on.. git tree: bpf console+strace: https://syzkaller.appspot.com/x/log.txt?x=127ca1f9580000 kernel config: https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e dashboard link: https://syzkaller.appspot.com/bug?extid=4bd730aede2791e40bdf compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17caf749580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=115c9f9e580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/e4f2d0fa738f/disk-15071f2a.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/508ad5098ef2/vmlinux-15071f2a.xz kernel image: https://storage.googleapis.com/syzbot-assets/c3f06d5bc6b9/bzImage-15071f2a.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+4bd730aede2791e40bdf@syzkaller.appspotmail.com ============================= WARNING: suspicious RCU usage syzkaller #0 Not tainted ----------------------------- net/netfilter/nf_conntrack_netlink.c:3393 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 locks held by syz-executor381/5628: 2, last CPU#1: #0: ffffffff9aee42a0 (nfnl_subsys_ctnetlink_exp){+.+.}-{4:4}, at: nfnl_lock net/netfilter/nfnetlink.c:96 [inline] #0: ffffffff9aee42a0 (nfnl_subsys_ctnetlink_exp){+.+.}-{4:4}, at: nfnetlink_rcv_msg+0xa69/0x12b0 net/netfilter/nfnetlink.c:293 #1: ffffffff8ea74d58 (nf_conntrack_expect_lock){+...}-{3:3}, at: spin_lock_bh include/linux/spinlock.h:353 [inline] #1: ffffffff8ea74d58 (nf_conntrack_expect_lock){+...}-{3:3}, at: nf_ct_expect_iterate_net+0x38/0x180 net/netfilter/nf_conntrack_expect.c:623 stack backtrace: CPU: 1 UID: 0 PID: 5628 Comm: syz-executor381 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: <TASK> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 lockdep_rcu_suspicious+0x140/0x1d0 kernel/locking/lockdep.c:6972 expect_iter_name+0xfb/0x100 net/netfilter/nf_conntrack_netlink.c:3393 nf_ct_expect_iterate_net+0xf2/0x180 net/netfilter/nf_conntrack_expect.c:633 ctnetlink_del_expect+0x45d/0x640 net/netfilter/nf_conntrack_netlink.c:3455 nfnetlink_rcv_msg+0xcc2/0x12b0 net/netfilter/nfnetlink.c:300 netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2556 nfnetlink_rcv+0x2b9/0x28c0 net/netfilter/nfnetlink.c:667 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1900 sock_sendmsg_nosec+0x13a/0x180 net/socket.c:800 __sock_sendmsg net/socket.c:815 [inline] ____sys_sendmsg+0x54e/0x850 net/socket.c:2713 ___sys_sendmsg+0x2a5/0x360 net/socket.c:2767 __sys_sendmsg net/socket.c:2799 [inline] __do_sys_sendmsg net/socket.c:2804 [inline] __se_sys_sendmsg net/socket.c:2802 [inline] __x64_sys_sendmsg+0x1b1/0x290 net/socket.c:2802 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb7651a5649 Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 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 d8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc2a17f2a8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb7651a5649 RDX: 0000000020000080 RSI: 0000200000000300 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000000000006 R09: 0000000000000006 R10: 0000000000000006 R11: 0000000000000246 R12: 0000000000000000 R13: 431bde82d7b634db R14: 00007fb765238c40 R15: 0000000000000002 </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 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