Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3661912pxj; Tue, 15 Jun 2021 06:05:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyLaqs0GqRDw7xElZvVu6jeR34FmgbO0LXKmc1enKxLnC5Eh61LA/rHd6m0W/hNgZPpiqww X-Received: by 2002:a6b:b20a:: with SMTP id b10mr52968iof.36.1623762304097; Tue, 15 Jun 2021 06:05:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623762304; cv=none; d=google.com; s=arc-20160816; b=mU7sm+pofdkgazVE8w/v9PT9s2rRxomsmbTrl6OHpQwSPvm/HmT5GB/p0BoIl7yHgq LJb/7reMw7CjUx6akBqbAkSQuTId20cxWZSqY9Vz8yiK2fH5vTQWF1saAwQi/hnA25MQ jFPqk5qicirvoSL6qqmKV9+CFkpX+Yy0MO/8W2IauZYt2GSsMU3iS5+FLNjtdxc0cnFB oGV1JzhtGP58CreFB9AjAoF5nVK9qhUE3H9BncchGltDMtvey5p8YRtqX/9o2wGKEe7u 4Lu/VbvJiaZaAl204rGNgWn91IGnMgX5gVvVXK7tjYUeft+pQOfi0HS3GGdlNtiolzpo z9SA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=TEvVhDaDzPUavWveqhgjFubWZRL+Yd56wIK4KtGPG/Q=; b=dr7t1RFJ0/CKAW+NKXrWJ++um23PVDEWXOvsFlV9qob8PJ8XUlq5BSVp+ZuaVQB197 31D9BSAJKa7d1HKWvjtiDSlJCM+l87gBFCvA4ibshDeemrFNslOQW2IqgKh5W3ZkoV64 SgU6Yjln5bYXGXKy3H7dHKi8+0wH9WB1l1Olw50wAA3g6C015HVi1maNR8OTw0OHgaH0 B+GkTujxcrVcv5mW9HpDIHqFsZNTUSfrFL5C34DKxYrelxkBTm22l3hGcAuL2+m/QluY omHcWaM6XclyafcvplI/hvMnivPnJeoDiM4+MZKldHDYcXHGJHK3M67aPDDWu4QAWCdZ 12hw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=aWscDUez; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=VvvKOsyo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w21si1242258jal.38.2021.06.15.06.04.50; Tue, 15 Jun 2021 06:05:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=aWscDUez; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=VvvKOsyo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230239AbhFONFM (ORCPT + 99 others); Tue, 15 Jun 2021 09:05:12 -0400 Received: from new3-smtp.messagingengine.com ([66.111.4.229]:52869 "EHLO new3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229951AbhFONFL (ORCPT ); Tue, 15 Jun 2021 09:05:11 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 7EE21580950; Tue, 15 Jun 2021 09:03:06 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 15 Jun 2021 09:03:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=TEvVhDaDzPUavWveqhgjFubWZRL +Yd56wIK4KtGPG/Q=; b=aWscDUez2rKtKzVjYpBKUkl7PENoJoDkUpT/J9qm9in PJPAGjk12kb7FvCg5OlDKZD/9yWqB7UJL9Kg5eYEdUdjRoZCxKG/FeQBhr3uSYi+ 6OFiFEW7bwKnLQKLnDmseKJj6lfqIcxeTiPhcXioaJrsau9dDem3uvANn4fqJ6Ef AYUwgxLo3XPs6nRDRqF2ZhpHQonvSyK++EyiBsP5wpBpYIWkqbBc+Hvyq6DUeSEX Q8fTBmlt1qq09Hzw1FQ0pftw/rVVLbszdW4ClgCuTtZWSPDxXvEIAYJfNEIBQzXm y5MAA67Vs9ojThSJjgS4KnlRnf3MAjJtrs37t45b7Ng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=TEvVhD aDzPUavWveqhgjFubWZRL+Yd56wIK4KtGPG/Q=; b=VvvKOsyoDMrUPRQOHlb5rU CoTrdGNHpltSZ9vPpvIbltTSv6YM2R719n4Bak2aIsC3Sxb3XJXGh2SNy1Xj+MX7 K03HK9DRw00YUnNbvxYjVd9QPRO4TvrmvpJXwy35PJnnpUajcPHXYwtWEu6umZRJ jayQPEpeccZy8mCdmgNCegz8uEvFX3uEj+0ytIs+ekyiqbSIvOxFrCjHY28IlV+3 SqkTIWhfeUyTZctegY/1rWQxR+LIe1PGnhJEWKqeB6EGYWW57jVHJ46SNQZRfA+7 xlRA0CHKAdnR7C0Saiw//9rDAmxnC8RbHRbRzCVVDrHfYgFlSNG3RNapAWCk6X/g == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvjedgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevueehje fgfffgiedvudekvdektdelleelgefhleejieeugeegveeuuddukedvteenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhh drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Jun 2021 09:03:05 -0400 (EDT) Date: Tue, 15 Jun 2021 15:03:03 +0200 From: Greg KH To: Dongliang Mu Cc: Steve Glendinning , "David S. Miller" , Jakub Kicinski , Pavel Skripkin , netdev@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel Subject: Re: [PATCH] net: usb: fix possible use-after-free in smsc75xx_bind Message-ID: References: <20210614153712.2172662-1-mudongliangabcd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 15, 2021 at 08:07:10PM +0800, Dongliang Mu wrote: > On Tue, Jun 15, 2021 at 7:12 PM Greg KH wrote: > > > > On Tue, Jun 15, 2021 at 06:24:17PM +0800, Dongliang Mu wrote: > > > On Tue, Jun 15, 2021 at 6:10 PM Dongliang Mu wrote: > > > > > > > > On Tue, Jun 15, 2021 at 5:44 PM Greg KH wrote: > > > > > > > > > > On Tue, Jun 15, 2021 at 03:56:32PM +0800, Dongliang Mu wrote: > > > > > > On Tue, Jun 15, 2021 at 3:38 PM Greg KH wrote: > > > > > > > > > > > > > > On Mon, Jun 14, 2021 at 11:37:12PM +0800, Dongliang Mu wrote: > > > > > > > > The commit 46a8b29c6306 ("net: usb: fix memory leak in smsc75xx_bind") > > > > > > > > fails to clean up the work scheduled in smsc75xx_reset-> > > > > > > > > smsc75xx_set_multicast, which leads to use-after-free if the work is > > > > > > > > scheduled to start after the deallocation. In addition, this patch also > > > > > > > > removes one dangling pointer - dev->data[0]. > > > > > > > > > > > > > > > > This patch calls cancel_work_sync to cancel the schedule work and set > > > > > > > > the dangling pointer to NULL. > > > > > > > > > > > > > > > > Fixes: 46a8b29c6306 ("net: usb: fix memory leak in smsc75xx_bind") > > > > > > > > Signed-off-by: Dongliang Mu > > > > > > > > --- > > > > > > > > drivers/net/usb/smsc75xx.c | 3 +++ > > > > > > > > 1 file changed, 3 insertions(+) > > > > > > > > > > > > > > > > diff --git a/drivers/net/usb/smsc75xx.c b/drivers/net/usb/smsc75xx.c > > > > > > > > index b286993da67c..f81740fcc8d5 100644 > > > > > > > > --- a/drivers/net/usb/smsc75xx.c > > > > > > > > +++ b/drivers/net/usb/smsc75xx.c > > > > > > > > @@ -1504,7 +1504,10 @@ static int smsc75xx_bind(struct usbnet *dev, struct usb_interface *intf) > > > > > > > > return 0; > > > > > > > > > > > > > > > > err: > > > > > > > > + cancel_work_sync(&pdata->set_multicast); > > > > > > > > kfree(pdata); > > > > > > > > + pdata = NULL; > > > > > > > > > > > > > > Why do you have to set pdata to NULL afterward? > > > > > > > > > > > > > > > > > > > It does not have to. pdata will be useless when the function exits. I > > > > > > just referred to the implementation of smsc75xx_unbind. > > > > > > > > > > It's wrong there too :) > > > > > > > > /: I will fix such two sites in the v2 patch. > > > > > > Hi gregkh, > > > > > > If the schedule_work is not invoked, can I call > > > ``cancel_work_sync(&pdata->set_multicast)''? > > > > Why can you not call this then? > > I don't know the internal of schedule_work and cancel_work_sync, so I > ask this question to confirm my patch does not introduce any new > issues. Please see the documentation for this function for all of the details. It is in kernel/workqueue.c