mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tao Chen <chentao.kernel@linux.alibaba.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	Petr Machata <petrm@nvidia.com>,
	Kees Cook <keescook@chromium.org>,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] netlink: Fix potential skb memleak in netlink_ack
Date: Fri, 4 Nov 2022 14:15:39 +0800	[thread overview]
Message-ID: <a0084580-7956-0825-42de-90c0b220cc21@linux.alibaba.com> (raw)
In-Reply-To: <20221102143953.001f1247@kernel.org>

在 2022/11/3 上午5:39, Jakub Kicinski 写道:
> On Wed,  2 Nov 2022 20:08:20 +0800 Tao Chen wrote:
>> We should clean the skb resource if nlmsg_put/append failed
>> , so fix it.
> 
> The comma should be at the end of the previous line.
> But really the entire ", so fix it." is redundant.
> 
Thank you, i will pay attention next time
>> Fiexs: commit 738136a0e375 ("netlink: split up copies in the
>> ack construction")
> 
> Please look around to see how to correctly format a Fixes tag
> (including not line wrapping it).
> 
> How did you find this bug? An automated tool? Syzbot?
> 
> One more note below on the code itself.
> 
This was found by the coverity tool, i will add it.
>> Signed-off-by: Tao Chen <chentao.kernel@linux.alibaba.com>
>> ---
>>   net/netlink/af_netlink.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
>> index c6b8207e..9d73dae 100644
>> --- a/net/netlink/af_netlink.c
>> +++ b/net/netlink/af_netlink.c
>> @@ -2500,7 +2500,7 @@ void netlink_ack(struct sk_buff *in_skb, struct nlmsghdr *nlh, int err,
>>   
>>   	skb = nlmsg_new(payload + tlvlen, GFP_KERNEL);
>>   	if (!skb)
>> -		goto err_bad_put;
>> +		goto err_skb;
>>   
>>   	rep = nlmsg_put(skb, NETLINK_CB(in_skb).portid, nlh->nlmsg_seq,
>>   			NLMSG_ERROR, sizeof(*errmsg), flags);
>> @@ -2528,6 +2528,8 @@ void netlink_ack(struct sk_buff *in_skb, struct nlmsghdr *nlh, int err,
>>   	return;
>>   
>>   err_bad_put:
>> +	kfree_skb(skb);
> 
> Please use nlmsg_free() since we allocated with nlmsg_new().
> 
Ok, i will send it in v2.
>> +err_skb:
>>   	NETLINK_CB(in_skb).sk->sk_err = ENOBUFS;
>>   	sk_error_report(NETLINK_CB(in_skb).sk);
>>   }

      reply	other threads:[~2022-11-04  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 12:08 Tao Chen
2022-11-02 15:05 ` Kees Cook
2022-11-02 21:39 ` Jakub Kicinski
2022-11-04  6:15   ` Tao Chen [this message]

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=a0084580-7956-0825-42de-90c0b220cc21@linux.alibaba.com \
    --to=chentao.kernel@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=johannes@sipsolutions.net \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=socketcan@hartkopp.net \
    /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

all inboxes | Powered by JetHome®