Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3580477pxj; Tue, 15 Jun 2021 04:13:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9nAAn094kg1P3Y+Ei5OTVVFGujBZPKOb4gwPh5OTiEvpWZ53sdxbV2z7hYX0muyKJQztM X-Received: by 2002:a17:906:edb3:: with SMTP id sa19mr20023649ejb.75.1623755632438; Tue, 15 Jun 2021 04:13:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623755632; cv=none; d=google.com; s=arc-20160816; b=sXnqi0ZuDCKpz+eEWBINfD/fu043Z8bYr5OiislSddxvoXTvrf4eZqmhyLnD3vLjok fM3QfDd/gVifLTWrzqj1mSc7EgyxcapxFe6TQ+rHX3LC4BEengpZKYvR58ngmiAGheWy XNL0fTfzSrz4/WOoOmlw7HxAB/lYvuNysX1TrFSQQ9IL/EwwMK/LvZfjgBJE4KVjVNv0 Pf5ufxVBhH9suLDvQwbVhsDkzp0dXcKqVJ8qsmeNZOtzJadvuNy9DMScXa/53xoUThhH Lw32YlDwRQdQ5kRMAJ80xFywRxaevkaBW70wiJn7u92GfpusdlhFz1I7SxWW1t8J0zLd 3KBQ== 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=9Q6KDp2HWna3rxZivpNB7NpzF6dwHBZaHCxz9AOstAo=; b=q/OLkXzEGf0uudbERfiD2y2lPT12E4bsApzRsjxuuGMqofzxWOrWaHnddul15NINvA l3ifnnviQSBbEQtuiLaB1SmKtVHuU/LsdbeNzLuAi0CZzbxYg5G9mjBaVezu80lXPoEN dcEloakZeeBAprSeaxMPDnkVIpaInClRh/idab1xmZycZGyGqU5PEaHNrcKc0idqBRcb 0mxI5CeNtt42F85NZ1mcJHfQRbdKg8qL2ANy/aWEgFYgaFgvCgsdy/u+45rtxvpAhPyU pBK22R3fSYY6yuC71QT9Xa+l+9AZwE2yTw/BmvHizVTFpDA4NQnsfTzzsdVXM7XXkHRM ba9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=VO1TcpCO; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=W1FCPA7R; 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 c12si16460996edx.372.2021.06.15.04.13.29; Tue, 15 Jun 2021 04:13:52 -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=VO1TcpCO; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=W1FCPA7R; 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 S230152AbhFOLOe (ORCPT + 99 others); Tue, 15 Jun 2021 07:14:34 -0400 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:60045 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229601AbhFOLO2 (ORCPT ); Tue, 15 Jun 2021 07:14:28 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 2909B5808D9; Tue, 15 Jun 2021 07:12:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Tue, 15 Jun 2021 07:12:23 -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=9Q6KDp2HWna3rxZivpNB7NpzF6d wHBZaHCxz9AOstAo=; b=VO1TcpCOxfXH3sxQowoQcl75VH48aPea2qp+QAdYfyN /YH7qGFT+GA1PsFaIbHL7xLq+M/t8KGQinALWSK3ocGOq3mRg6PFtGY6WXIdpXCK XYcx82cKdjEB2OKfrMfglX7zpcQk+M6Yu02RBEFA3pBVVd6rplPtRyLo81WlXVeb 5Z5jf/BmyYxiCGw20t+o1P/j9IIz34aMOrOXDdDwFUHdRNnO2fB2+63ACXg4ckhh LdM33XMDpmcI4Qvhc/cJhTg1bR/B/ykLQ5buUUHdMCBZSPXPGuA0aq/zqxONI2yl Qs4VEiSKSmzs168xEtVNJ+yum1vDfvPVHr2rTak1X7g== 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=9Q6KDp 2HWna3rxZivpNB7NpzF6dwHBZaHCxz9AOstAo=; b=W1FCPA7R8Q4QZWMjtIOYbO 3essXw18DAQP9FvCgS6bIY37SDq3hNKzEpbuyM8etfT0SjPDoMbh+c0goBNMguWp TcEahIFdsLbm68tksyY+anScdXDmiAygPrjGQxoaAQHetdW78vEgQhmfk+qSxilQ 5oPu+z+8zGj5BmleSskJxNuO8PMCWF1kLgqD2prfFNdax09KiI4nQ+eiw7veW/iA Zcd3NEWWeSydTW+qwDXQmaaz5n02y64eZaOZEHdrextyWRJCeyIuU1jmV+uLznKt SSPcj/0yBkyfptjxOfW49U5XRQprEO58o2J3Moo6RQC9ubBl4fqpG1dX5NP/AAZA == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvjedgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdortddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevhefgje eitdfffefhvdegleeigeejgeeiffekieffjeeflefhieegtefhudejueenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhh drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Jun 2021 07:12:22 -0400 (EDT) Date: Tue, 15 Jun 2021 13:12:20 +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 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? Did you try it and see? thanks, greg k-h