From: Simon Horman <horms@kernel.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, edumazet@google.com, mkl@pengutronix.de,
Ziyang Xuan <william.xuanziyang@huawei.com>
Subject: Re: [NET 2/2] can: raw: add missing refcount for memory leak fix
Date: Tue, 22 Aug 2023 22:08:04 +0200 [thread overview]
Message-ID: <20230822200804.GC3523530@kernel.org> (raw)
In-Reply-To: <03a97ce3-ee82-5cc0-52cd-2501eeebb240@hartkopp.net>
On Tue, Aug 22, 2023 at 06:45:25PM +0200, Oliver Hartkopp wrote:
>
>
> On 22.08.23 09:59, Simon Horman wrote:
> > On Mon, Aug 21, 2023 at 04:45:47PM +0200, Oliver Hartkopp wrote:
> > > Commit ee8b94c8510c ("can: raw: fix receiver memory leak") introduced
> > > a new reference to the CAN netdevice that has assigned CAN filters.
> > > But this new ro->dev reference did not maintain its own refcount which
> > > lead to another KASAN use-after-free splat found by Eric Dumazet.
> > >
> > > This patch ensures a proper refcount for the CAN nedevice.
> > >
> > > Fixes: ee8b94c8510c ("can: raw: fix receiver memory leak")
> > > Reported-by: Eric Dumazet <edumazet@google.com>
> > > Cc: Ziyang Xuan <william.xuanziyang@huawei.com>
> > > Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> >
> > ...
> >
> > > @@ -443,44 +448,56 @@ static int raw_bind(struct socket *sock, struct sockaddr *uaddr, int len)
> > > if (!dev) {
> > > err = -ENODEV;
> > > goto out;
> > > }
> > > if (dev->type != ARPHRD_CAN) {
> > > - dev_put(dev);
> > > err = -ENODEV;
> > > - goto out;
> > > + goto out_put_dev;
> > > }
> > > +
> > > if (!(dev->flags & IFF_UP))
> > > notify_enetdown = 1;
> > > ifindex = dev->ifindex;
> > > /* filters set by default/setsockopt */
> > > err = raw_enable_allfilters(sock_net(sk), dev, sk);
> > > - dev_put(dev);
> > > + if (err)
> > > + goto out_put_dev;
> > > +
> > > } else {
> > > ifindex = 0;
> > > /* filters set by default/setsockopt */
> > > err = raw_enable_allfilters(sock_net(sk), NULL, sk);
> > > }
> > > if (!err) {
> > > if (ro->bound) {
> > > /* unregister old filters */
> > > - if (ro->dev)
> > > + if (ro->dev) {
> > > raw_disable_allfilters(dev_net(ro->dev),
> > > ro->dev, sk);
> > > - else
> > > + /* drop reference to old ro->dev */
> > > + netdev_put(ro->dev, &ro->dev_tracker);
> > > + } else {
> > > raw_disable_allfilters(sock_net(sk), NULL, sk);
> > > + }
> > > }
> > > ro->ifindex = ifindex;
> > > ro->bound = 1;
> > > + /* bind() ok -> hold a reference for new ro->dev */
> > > ro->dev = dev;
> > > + if (ro->dev)
> > > + netdev_hold(ro->dev, &ro->dev_tracker, GFP_KERNEL);
> > > }
> > > - out:
> > > +out_put_dev:
> > > + /* remove potential reference from dev_get_by_index() */
> > > + if (dev)
> > > + dev_put(dev);
> >
> > Hi Oliver,
> >
> > this is possibly not worth a respin, but there is no need to check if dev
> > is NULL before calling dev_put(), dev_put() will effectively be a no-op
> > with a NULL argument.
> >
>
> Hi Simon,
>
> thanks for your feedback.
>
> In fact I had in mind that someone recently removed some of these "if (dev)"
> statements before "dev_put(dev)" in the netdev subtree.
>
> The reason why I still wanted to point out this check is because of dev ==
> NULL is also a valid value for CAN_RAW sockets that are not bound to a
> specific netdev but to 'ALL' CAN netdevs.
>
> So it was more like a documentation purpose than a programming need.
>
> As you don't see a need for a respin too, I can send a patch to can-next to
> remove it, if that fits for you.
Thanks Oliver, that would be fine by me.
next prev parent reply other threads:[~2023-08-22 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 14:45 [NET 0/2] CAN fixes for 6.5-rc7 Oliver Hartkopp
2023-08-21 14:45 ` [NET 1/2] can: isotp: fix support for transmission of SF without flow control Oliver Hartkopp
2023-08-21 14:45 ` [NET 2/2] can: raw: add missing refcount for memory leak fix Oliver Hartkopp
2023-08-22 7:59 ` Simon Horman
2023-08-22 16:45 ` Oliver Hartkopp
2023-08-22 20:08 ` Simon Horman [this message]
2023-08-23 0:30 ` [NET 0/2] CAN fixes for 6.5-rc7 patchwork-bot+netdevbpf
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=20230822200804.GC3523530@kernel.org \
--to=horms@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=william.xuanziyang@huawei.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;
as well as URLs for NNTP newsgroup(s).