Netdev List
 help / color / mirror / Atom feed
* [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit()
@ 2026-06-06  1:21 Jakub Kicinski
  2026-06-06 22:06 ` Bobby Eshleman
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Jakub Kicinski @ 2026-06-06  1:21 UTC (permalink / raw)
  To: davem
  Cc: netdev, edumazet, pabeni, andrew+netdev, horms, Jakub Kicinski,
	Sashiko, bobbyeshleman, dw, daniel, razor, sdf, willemb, kaiyuanz

Sashiko flags that genlmsg_reply() always consumes the skb.
The error path calls nlmsg_free(rsp) so we can't jump directly
to it. Let's not unbind, just propagate the error to the user.
This is the typical way of handling genlmsg_reply() failures.
They shouldn't happen unless user does something silly like
calling the kernel with an already-full rcvbuf.

Reported-by: Sashiko <sashiko-bot@kernel.org>
Fixes: 170aafe35cb9 ("netdev: support binding dma-buf to netdevice")
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
CC: bobbyeshleman@gmail.com
CC: dw@davidwei.uk
CC: daniel@iogearbox.net
CC: razor@blackwall.org
CC: sdf@fomichev.me
CC: willemb@google.com
CC: kaiyuanz@google.com
---
 net/core/netdev-genl.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/net/core/netdev-genl.c b/net/core/netdev-genl.c
index b4d48f3672a5..11b0b91683d7 100644
--- a/net/core/netdev-genl.c
+++ b/net/core/netdev-genl.c
@@ -1095,8 +1095,6 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
 	genlmsg_end(rsp, hdr);
 
 	err = genlmsg_reply(rsp, info);
-	if (err)
-		goto err_unbind;
 
 	bitmap_free(rxq_bitmap);
 
@@ -1104,7 +1102,7 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
 
 	mutex_unlock(&priv->lock);
 
-	return 0;
+	return err < 0 ? err : 0;
 
 err_unbind:
 	net_devmem_unbind_dmabuf(binding);
-- 
2.54.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit()
  2026-06-06  1:21 [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit() Jakub Kicinski
@ 2026-06-06 22:06 ` Bobby Eshleman
  2026-06-08 13:21 ` Daniel Borkmann
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Bobby Eshleman @ 2026-06-06 22:06 UTC (permalink / raw)
  To: Jakub Kicinski
  Cc: davem, netdev, edumazet, pabeni, andrew+netdev, horms, Sashiko,
	dw, daniel, razor, sdf, willemb, kaiyuanz

On Fri, Jun 05, 2026 at 06:21:24PM -0700, Jakub Kicinski wrote:
> Sashiko flags that genlmsg_reply() always consumes the skb.
> The error path calls nlmsg_free(rsp) so we can't jump directly
> to it. Let's not unbind, just propagate the error to the user.
> This is the typical way of handling genlmsg_reply() failures.
> They shouldn't happen unless user does something silly like
> calling the kernel with an already-full rcvbuf.
> 
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Fixes: 170aafe35cb9 ("netdev: support binding dma-buf to netdevice")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: bobbyeshleman@gmail.com
> CC: dw@davidwei.uk
> CC: daniel@iogearbox.net
> CC: razor@blackwall.org
> CC: sdf@fomichev.me
> CC: willemb@google.com
> CC: kaiyuanz@google.com
> ---
>  net/core/netdev-genl.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/net/core/netdev-genl.c b/net/core/netdev-genl.c
> index b4d48f3672a5..11b0b91683d7 100644
> --- a/net/core/netdev-genl.c
> +++ b/net/core/netdev-genl.c
> @@ -1095,8 +1095,6 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
>  	genlmsg_end(rsp, hdr);
>  
>  	err = genlmsg_reply(rsp, info);
> -	if (err)
> -		goto err_unbind;
>  
>  	bitmap_free(rxq_bitmap);
>  
> @@ -1104,7 +1102,7 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
>  
>  	mutex_unlock(&priv->lock);
>  
> -	return 0;
> +	return err < 0 ? err : 0;
>  
>  err_unbind:
>  	net_devmem_unbind_dmabuf(binding);
> -- 
> 2.54.0
> 

Reviewed-by: Bobby Eshleman <bobbyeshleman@meta.com>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit()
  2026-06-06  1:21 [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit() Jakub Kicinski
  2026-06-06 22:06 ` Bobby Eshleman
@ 2026-06-08 13:21 ` Daniel Borkmann
  2026-06-08 13:43 ` Nikolay Aleksandrov
  2026-06-09  0:50 ` patchwork-bot+netdevbpf
  3 siblings, 0 replies; 5+ messages in thread
From: Daniel Borkmann @ 2026-06-08 13:21 UTC (permalink / raw)
  To: Jakub Kicinski, davem
  Cc: netdev, edumazet, pabeni, andrew+netdev, horms, Sashiko,
	bobbyeshleman, dw, razor, sdf, willemb, kaiyuanz

On 6/6/26 3:21 AM, Jakub Kicinski wrote:
> Sashiko flags that genlmsg_reply() always consumes the skb.
> The error path calls nlmsg_free(rsp) so we can't jump directly
> to it. Let's not unbind, just propagate the error to the user.
> This is the typical way of handling genlmsg_reply() failures.
> They shouldn't happen unless user does something silly like
> calling the kernel with an already-full rcvbuf.
> 
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Fixes: 170aafe35cb9 ("netdev: support binding dma-buf to netdevice")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit()
  2026-06-06  1:21 [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit() Jakub Kicinski
  2026-06-06 22:06 ` Bobby Eshleman
  2026-06-08 13:21 ` Daniel Borkmann
@ 2026-06-08 13:43 ` Nikolay Aleksandrov
  2026-06-09  0:50 ` patchwork-bot+netdevbpf
  3 siblings, 0 replies; 5+ messages in thread
From: Nikolay Aleksandrov @ 2026-06-08 13:43 UTC (permalink / raw)
  To: Jakub Kicinski, davem
  Cc: netdev, edumazet, pabeni, andrew+netdev, horms, Sashiko,
	bobbyeshleman, dw, daniel, sdf, willemb, kaiyuanz

On 06/06/2026 04:21, Jakub Kicinski wrote:
> Sashiko flags that genlmsg_reply() always consumes the skb.
> The error path calls nlmsg_free(rsp) so we can't jump directly
> to it. Let's not unbind, just propagate the error to the user.
> This is the typical way of handling genlmsg_reply() failures.
> They shouldn't happen unless user does something silly like
> calling the kernel with an already-full rcvbuf.
> 
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Fixes: 170aafe35cb9 ("netdev: support binding dma-buf to netdevice")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: bobbyeshleman@gmail.com
> CC: dw@davidwei.uk
> CC: daniel@iogearbox.net
> CC: razor@blackwall.org
> CC: sdf@fomichev.me
> CC: willemb@google.com
> CC: kaiyuanz@google.com
> ---
>   net/core/netdev-genl.c | 4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/net/core/netdev-genl.c b/net/core/netdev-genl.c
> index b4d48f3672a5..11b0b91683d7 100644
> --- a/net/core/netdev-genl.c
> +++ b/net/core/netdev-genl.c
> @@ -1095,8 +1095,6 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
>   	genlmsg_end(rsp, hdr);
>   
>   	err = genlmsg_reply(rsp, info);
> -	if (err)
> -		goto err_unbind;
>   
>   	bitmap_free(rxq_bitmap);
>   
> @@ -1104,7 +1102,7 @@ int netdev_nl_bind_rx_doit(struct sk_buff *skb, struct genl_info *info)
>   
>   	mutex_unlock(&priv->lock);
>   
> -	return 0;
> +	return err < 0 ? err : 0;
>   
>   err_unbind:
>   	net_devmem_unbind_dmabuf(binding);

Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit()
  2026-06-06  1:21 [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit() Jakub Kicinski
                   ` (2 preceding siblings ...)
  2026-06-08 13:43 ` Nikolay Aleksandrov
@ 2026-06-09  0:50 ` patchwork-bot+netdevbpf
  3 siblings, 0 replies; 5+ messages in thread
From: patchwork-bot+netdevbpf @ 2026-06-09  0:50 UTC (permalink / raw)
  To: Jakub Kicinski
  Cc: davem, netdev, edumazet, pabeni, andrew+netdev, horms,
	sashiko-bot, bobbyeshleman, dw, daniel, razor, sdf, willemb,
	kaiyuanz

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  5 Jun 2026 18:21:24 -0700 you wrote:
> Sashiko flags that genlmsg_reply() always consumes the skb.
> The error path calls nlmsg_free(rsp) so we can't jump directly
> to it. Let's not unbind, just propagate the error to the user.
> This is the typical way of handling genlmsg_reply() failures.
> They shouldn't happen unless user does something silly like
> calling the kernel with an already-full rcvbuf.
> 
> [...]

Here is the summary with links:
  - [net] netdev: fix double-free in netdev_nl_bind_rx_doit()
    https://git.kernel.org/netdev/net/c/c849de7d8757

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-06-09  0:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-06  1:21 [PATCH net] netdev: fix double-free in netdev_nl_bind_rx_doit() Jakub Kicinski
2026-06-06 22:06 ` Bobby Eshleman
2026-06-08 13:21 ` Daniel Borkmann
2026-06-08 13:43 ` Nikolay Aleksandrov
2026-06-09  0:50 ` patchwork-bot+netdevbpf

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox