From: Prithvi Tambewagh <activprithvi@gmail.com>
To: syzbot+3f2d46b6e62b8dd546d3@syzkaller.appspotmail.com,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, pabeni@redhat.com
Cc: linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Prithvi Tambewagh <activprithvi@gmail.com>
Subject: Testing for netrom: fix memory leak in nr_add_node
Date: Sat, 17 Jan 2026 19:56:32 +0530 [thread overview]
Message-ID: <20260117142632.180941-1-activprithvi@gmail.com> (raw)
In-Reply-To: <69694849.050a0220.58bed.0025.GAE@google.com>
#syz test upstream ea1013c1539270e372fc99854bc6e4d94eaeff66
Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
net/netrom/nr_route.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/netrom/nr_route.c b/net/netrom/nr_route.c
index b94cb2ffbaf8..20da41888151 100644
--- a/net/netrom/nr_route.c
+++ b/net/netrom/nr_route.c
@@ -176,6 +176,7 @@ static int __must_check nr_add_node(ax25_address *nr, const char *mnemonic,
hlist_add_head(&nr_neigh->neigh_node, &nr_neigh_list);
nr_neigh_hold(nr_neigh);
spin_unlock_bh(&nr_neigh_list_lock);
+ nr_neigh_put(nr_neigh);
}
if (quality != 0 && ax25cmp(nr, ax25) == 0 && !nr_neigh->locked)
base-commit: ea1013c1539270e372fc99854bc6e4d94eaeff66
--
2.34.1
next prev parent reply other threads:[~2026-01-17 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:04 [syzbot] [hams?] memory leak in nr_add_node syzbot
2026-01-16 2:19 ` Forwarded: [PATCH] netrom: fix memory leak in nr_add_node() syzbot
2026-01-16 3:40 ` syzbot
2026-01-16 7:42 ` syzbot
2026-01-16 8:28 ` syzbot
2026-01-16 8:59 ` syzbot
2026-01-16 9:39 ` syzbot
2026-01-16 12:51 ` syzbot
2026-01-17 14:26 ` Prithvi Tambewagh [this message]
2026-01-17 17:00 ` [syzbot] [hams?] memory leak in nr_add_node syzbot
2026-01-19 21:06 ` Testing for netrom: fix " F6BVP
2026-01-20 3:37 ` David Ranch
2026-01-20 16:00 ` Prithvi
2026-01-20 21:02 ` F6BVP
2026-01-22 17:27 ` Prithvi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260117142632.180941-1-activprithvi@gmail.com \
--to=activprithvi@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+3f2d46b6e62b8dd546d3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox