From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f80.google.com (mail-ot1-f80.google.com [209.85.210.80]) (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 3C90AEACD for ; Thu, 15 Jan 2026 20:04:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.80 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768507467; cv=none; b=UqC3fLXimScTm476GKtWw6ueGpKfBWXS4vVyQJ8UUNOuGBw/VVIN18MGinHEeSA8QwSFMkctmqYRTnvwXtffHK6GYiXQFEOhj7R4BtTOHeVYiHqkuDnCpdPAAO8FeAfkKE49NbTYPgkoXtVhjvDhUWnHbdfsRxlxvy1xkZWI0hI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768507467; c=relaxed/simple; bh=rWBstfbzf1z7y4/sY4ZKVCSi1bwr3zlYRKvlnu4jqGw=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=mPJ1TLh+3dWe7jdyhF6sAIVjhmPt6ZPPsMJd08MbEOiMSiuU+a3Z6gcN3H46stJ32Pvhfmb9XYLSLQ/hgNn/3ZmkmJAOOEqJ2U5mhD8ZvhRPuHlrYur2rO/dzxMa3aPS+zZcPNh3SVfrooG+8677QPrJBQW8t9tZyqjZz7K9JCg= 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.210.80 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-ot1-f80.google.com with SMTP id 46e09a7af769-7cfd107ef0eso5088318a34.1 for ; Thu, 15 Jan 2026 12:04:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768507465; x=1769112265; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=crnuoM0pogZ/BTfdoYh6CD5pzgeMjwMohO7mQOnJJMY=; b=HqsW/LS/PQSIYTBnkczayZ61TeobNGjb172b3nK/DfSnRfu7WrUVzbVSo+5Sn9WxKT l8JEnOBFH51CejObRICwTcDEz6BLCxgxvli395OirOfSBGI1BA7QLIA9sIkRrSRzwc3l O+7Dc0nS2F4tafWJYQxKPoD2QDIqvABiF0+VgDJ6oDGrWpKUFAlJ3E+5DV6xQLVoUxUY Ajjjiml/WcitqWNap/x1TJmiSaehXvSyYhN6+woLOQMR19kt7JjLOdV9IKPY23Nr/JTg qmYx58m7Xt/O5y63SWodh4XINpZ1gFxx6gGUrgvP1ff1n9AB82XfnRvkfWJS9U9uHCL2 sGlw== X-Forwarded-Encrypted: i=1; AJvYcCXfPbzNEc35KhX7kqvCcj0ug+I5cDTjf0ATsJAXZEmwRKS31iTuBklE28Fxgw5r1EHon1iT8tA=@vger.kernel.org X-Gm-Message-State: AOJu0Yw1CPQmZiAckJc5ngIvGMrvO6S7YA+tn54Tf76aVqX1AM55Fcu0 /lLAEtISxtDsxb3KhpvfrurTCTvAPqO/4x7miKKUgEKc03uV1mHqAmZBEbQWwdWkliOrHBsxeiv Y5eszddX6KuUVG/XXxL56w/ffdPldo/OXNC+wcjcsXcyOKr9UB7LQEthZ4n4= Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:f015:b0:659:9a49:8f55 with SMTP id 006d021491bc7-6611796e949mr429357eaf.26.1768507465160; Thu, 15 Jan 2026 12:04:25 -0800 (PST) Date: Thu, 15 Jan 2026 12:04:25 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69694849.050a0220.58bed.0025.GAE@google.com> Subject: [syzbot] [hams?] memory leak in nr_add_node From: syzbot To: davem@davemloft.net, edumazet@google.com, horms@kernel.org, kuba@kernel.org, linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: ea1013c15392 Merge tag 'bpf-fixes' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=147cb184580000 kernel config: https://syzkaller.appspot.com/x/.config?x=d60836e327fd6756 dashboard link: https://syzkaller.appspot.com/bug?extid=3f2d46b6e62b8dd546d3 compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c839b4580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127cb184580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/5ee91238d53c/disk-ea1013c1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/b8eb70b8203f/vmlinux-ea1013c1.xz kernel image: https://storage.googleapis.com/syzbot-assets/3aed81c1b1c5/bzImage-ea1013c1.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/6e21e0104490/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+3f2d46b6e62b8dd546d3@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff88811b404b80 (size 64): comm "syz.0.17", pid 6071, jiffies 4294944872 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f88ea0ab): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4958 [inline] slab_alloc_node mm/slub.c:5263 [inline] __kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771 kmalloc_noprof include/linux/slab.h:957 [inline] nr_add_node+0x5bf/0x14b0 net/netrom/nr_route.c:146 nr_rt_ioctl+0xc32/0x16e0 net/netrom/nr_route.c:651 nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254 sock_do_ioctl+0x84/0x1a0 net/socket.c:1254 sock_ioctl+0x149/0x480 net/socket.c:1375 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff88811b404d00 (size 64): comm "syz.0.18", pid 6078, jiffies 4294944884 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 8f10725b): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4958 [inline] slab_alloc_node mm/slub.c:5263 [inline] __kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771 kmalloc_noprof include/linux/slab.h:957 [inline] nr_add_node+0x5bf/0x14b0 net/netrom/nr_route.c:146 nr_rt_ioctl+0xc32/0x16e0 net/netrom/nr_route.c:651 nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254 sock_do_ioctl+0x84/0x1a0 net/socket.c:1254 sock_ioctl+0x149/0x480 net/socket.c:1375 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f BUG: memory leak unreferenced object 0xffff88811b404f80 (size 64): comm "syz.0.19", pid 6086, jiffies 4294944897 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ cc cc cc cc cc cc 02 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 14b53e34): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4958 [inline] slab_alloc_node mm/slub.c:5263 [inline] __kmalloc_cache_noprof+0x3b2/0x570 mm/slub.c:5771 kmalloc_noprof include/linux/slab.h:957 [inline] nr_add_node+0x5bf/0x14b0 net/netrom/nr_route.c:146 nr_rt_ioctl+0xc32/0x16e0 net/netrom/nr_route.c:651 nr_ioctl+0x11f/0x1a0 net/netrom/af_netrom.c:1254 sock_do_ioctl+0x84/0x1a0 net/socket.c:1254 sock_ioctl+0x149/0x480 net/socket.c:1375 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF --- 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