[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166056061390.20212.5869065400117600776.git-patchwork-notify@kernel.org>
Date: Mon, 15 Aug 2022 10:50:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Xin Xiong <xiongx18@...an.edu.cn>
Cc: davem@...emloft.net, yoshfuji@...ux-ipv6.org, dsahern@...nel.org,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
praveen5582@...il.com, zxu@...kedin.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, yuanxzhang@...an.edu.cn,
tanxin.ctf@...il.com
Subject: Re: [PATCH] net: fix potential refcount leak in ndisc_router_discovery()
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:
On Sat, 13 Aug 2022 20:49:08 +0800 you wrote:
> The issue happens on specific paths in the function. After both the
> object `rt` and `neigh` are grabbed successfully, when `lifetime` is
> nonzero but the metric needs change, the function just deletes the
> route and set `rt` to NULL. Then, it may try grabbing `rt` and `neigh`
> again if above conditions hold. The function simply overwrite `neigh`
> if succeeds or returns if fails, without decreasing the reference
> count of previous `neigh`. This may result in memory leaks.
>
> [...]
Here is the summary with links:
- net: fix potential refcount leak in ndisc_router_discovery()
https://git.kernel.org/netdev/net/c/7396ba87f1ed
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists