From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f71.google.com (mail-oo1-f71.google.com [209.85.161.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6FE332E228D for ; Wed, 15 Apr 2026 12:32:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.71 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776256359; cv=none; b=qVAidv+9/HEoaWuQiarkpJnn9JWtl0hqrEaIymqlUe5WfFJkATsq7m4ExfnMy1HxugFLjXqD3U2qajt6z0PyeALKrnxU7fRg2mcrtCfwrzxTS5hsn1lmyM227os0xoZy347t5KTL+BkLTBc5nEpGblJtBmFCVR2JLGYpsclo1i8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776256359; c=relaxed/simple; bh=mM2Lm4AuVorwjrbxW1oOiut+TGjlshlWQ2acbQ+Itgg=; h=MIME-Version:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=iNrnvif89Z9hEwCB0NV2TDBi1cJB6F8TQqGiqmm/QmHNwNdd5TOS1Q8jATPOOpO05a7lrIQxA84iZdaJwf1FjTb6VgX5tuc5+yrPk/sMbA4fWv/v9qubTLrliV5m7m71dDZijgYiYuQM0gGPZssqe+PPOze2a67q+ufirxLMfAQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.71 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f71.google.com with SMTP id 006d021491bc7-692d2ad19edso1812642eaf.2 for ; Wed, 15 Apr 2026 05:32:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776256356; x=1776861156; h=cc:to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=T2Xd6TwtA/ovAg/2LMxsJEoZX/lJWdNw63m3oL4dsC4=; b=UlwuZv/ToBh/zNtC0VtWld5lKiNDyYd3J0duhzC4MkTzAJX2IH+moUQ07vbEC42hRq s7yZ8xwjBPT90EuCp3w3WA58whCCk6DCUHKpCUuX/rDfG8oLpVurZrLx66ap4eJTMV64 /Sl98TAa5WaaAkoSCs2kgvzajRck0Pr5AA6zCl2fDg7KoiZPc8l6Jf/bGmDaoTB87v4G CvVXlvMOHtvlXMIEWIu0GWcyr5MWgJjXJIzrjN5QzID2fjcmVXyraCZ3oTqGmFDfKCul XuQ0sKFjLpbXZgwtYXZXAwzCVU8pZuynLTJ8j7Q797pO5K19VSj6nUQjXL0Ag843Vf// mwBA== X-Gm-Message-State: AOJu0Yygc664TJgCR59BIJtTUmVyZji/g5hRIQfBwaGzLlFuzUW77cL8 y5RuTI+b10NT6wwIzsmUeA1PgHnXW1DOmsnaUGQca9LwqM2nEFvxxNccT/pD5gfX3VZQdUN+xjc a4L6bzBqvzgrQ0Tbfmp5r8I8+mul2g3LS4WLdv6C4H8rxHwxB1X9t/lbDYb8= Precedence: bulk X-Mailing-List: syzbot@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:987:b0:685:f11f:edba with SMTP id 006d021491bc7-68be604a40fmr10904004eaf.20.1776256356510; Wed, 15 Apr 2026 05:32:36 -0700 (PDT) Date: Wed, 15 Apr 2026 05:32:36 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69df8564.a70a0220.259bc5.000a.GAE@google.com> Subject: [moderation/CI] Re: [PATCH net] tipc: fix UAF race in tipc_mon_peer_up/down/remove_peer vs bearer teardown From: syzbot ci To: syzkaller-upstream-moderation@googlegroups.com Cc: syzbot@lists.linux.dev Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v1] [PATCH net] tipc: fix UAF race in tipc_mon_peer_up/down/remove_peer vs bearer teardown https://lore.kernel.org/all/20260415061211.45530-1-95986478+SnailSploit@users.noreply.github.com * [PATCH] [PATCH net] tipc: fix UAF race in tipc_mon_peer_up/down/remove_peer vs bearer teardown and found the following issue: WARNING: suspicious RCU usage in tipc_mon_delete Full report is available here: https://ci.syzbot.org/series/6267bc07-4172-4821-b3e5-dac381479d9d *** WARNING: suspicious RCU usage in tipc_mon_delete tree: net-next URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git base: 35c2c39832e569449b9192fa1afbbc4c66227af7 arch: amd64 compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8 config: https://ci.syzbot.org/builds/a29dabe7-96d8-4072-bc2c-d798a349301e/config syz repro: https://ci.syzbot.org/findings/f144d75a-7c29-41a1-988e-09892a89baa1/syz_repro tipc: Disabling bearer ============================= WARNING: suspicious RCU usage syzkaller #0 Not tainted ----------------------------- net/tipc/monitor.c:108 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.2.19/5962: #0: ffffffff8fbcba48 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline] #0: ffffffff8fbcba48 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3438 stack backtrace: CPU: 1 UID: 0 PID: 5962 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 lockdep_rcu_suspicious+0x13f/0x1d0 kernel/locking/lockdep.c:6876 tipc_monitor_rcu_bh+0xf5/0x110 net/tipc/monitor.c:108 get_self net/tipc/monitor.c:209 [inline] tipc_mon_delete+0x10b/0x4d0 net/tipc/monitor.c:704 tipc_l2_device_event+0x370/0x680 net/tipc/bearer.c:-1 notifier_call_chain+0x1be/0x400 kernel/notifier.c:85 call_netdevice_notifiers_extack net/core/dev.c:2287 [inline] call_netdevice_notifiers net/core/dev.c:2301 [inline] unregister_netdevice_many_notify+0x17a5/0x22c0 net/core/dev.c:12464 unregister_netdevice_many net/core/dev.c:12527 [inline] unregister_netdevice_queue+0x31f/0x360 net/core/dev.c:12337 unregister_netdevice include/linux/netdevice.h:3427 [inline] __tun_detach+0x6d9/0x15d0 drivers/net/tun.c:621 tun_detach drivers/net/tun.c:637 [inline] tun_chr_close+0x10a/0x1c0 drivers/net/tun.c:3438 __fput+0x44f/0xa70 fs/file_table.c:469 task_work_run+0x1d9/0x270 kernel/task_work.c:233 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] __exit_to_user_mode_loop kernel/entry/common.c:67 [inline] exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:98 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline] syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline] do_syscall_64+0x32d/0xf80 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f7b26d9c819 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffec30cee78 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00007ffec30cef60 RCX: 00007f7b26d9c819 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 0000000000011900 R08: 0000000000000001 R09: 0000000000000000 R10: 0000001b2e520000 R11: 0000000000000246 R12: 00007ffec30cefa0 R13: 00007f7b27015fac R14: 000000000001193b R15: 00007f7b27015fa0 *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: syzbot@syzkaller.appspotmail.com --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at syzkaller@googlegroups.com. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported. The email will later be sent to: [jmaloy@redhat.com kai.aizen.dev@gmail.com kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com stable@vger.kernel.org tipc-discussion@lists.sourceforge.net ying.xue@windriver.com] If the report looks fine to you, reply with: #syz upstream If the report is a false positive, reply with #syz invalid