Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp178990pxb; Mon, 13 Sep 2021 16:21:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw2xtiNUuMgm5v7+aGtEae52myf/IawGHCgI3KcPyqHSAffgwqM5D6dSdOmokKJYTdDndkA X-Received: by 2002:a05:6402:150a:: with SMTP id f10mr15849157edw.318.1631575300628; Mon, 13 Sep 2021 16:21:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631575300; cv=none; d=google.com; s=arc-20160816; b=zefoUY5xNnFLPqsA54nfD9BYzfflzByncitNgt/GTmCWXOTyaczn5aVwfwcZIdKNRt z6zX1ncHdMRmknPTxpyui0R6aJywSomOdlkLcG7q5KNdpB+ZxW34/sylPMoIbhLqcYP1 CezvbyCHk0crrfiT18sPB5ViWwCkBokLic1ubb7WLkF5XoW0YXbCcYF1ozCTz5PFDaAK U//5JNn1pyk2TvEvPGbKwjEzkY6HR8WGdZsmFylDlbuVXMhttbOWKCsucmCo5C+cBOXf iF/4Rvj8cS8amkmc5zA83T6znCwx7GVVGYnqFO1rPFioANh3kgywvVZWB5SeXox3ip5v 1aNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=pjSVpAuKLubHIajPsrQwBEzqROdzWkLBGS3yoCttANY=; b=g+yT3nDwOY9N3Ej28SDnR/XdRG4AOUaJnjRI+P6rN6Al4gdZ5XI4r7LE8zqfJ/nsPR f/4mZFUeSAzuFJ38m3Tp7QUrCmwBRJ+uePN+kLWqeOGJ8X0ev6fnk671pUwDHRWSViAB YX1JAayWxbt1clySFijYPlEv1kp0Y9kN8tCRHMCUpj235nwX8s9onFO5qVsS82uSnPQF 7+wyAdnKEMU9fWNAGXU2LSxm9fyyN6AVtLc6lpkevmN+K/qe3xPNxGN/f3dF3yV5SURg 2ZM7chfATT92TLQ6GKr+ibtZW7S7csLodsm/rVaqGLyXcT7uvNKVZBro31xWqVSjZSV8 n2CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=cp4NGzHR; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r23si7183688edq.233.2021.09.13.16.21.16; Mon, 13 Sep 2021 16:21:40 -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=@linuxfoundation.org header.s=korg header.b=cp4NGzHR; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346596AbhIMOrs (ORCPT + 99 others); Mon, 13 Sep 2021 10:47:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:60464 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347646AbhIMOmK (ORCPT ); Mon, 13 Sep 2021 10:42:10 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3BCC4604DC; Mon, 13 Sep 2021 13:56:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631541396; bh=cHZumzlrM6+tZYz5z+PpTZySAuJUyF2i/7mgvc4lVKY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cp4NGzHRYfruCJcdjiAI5liGt7GvmG1P77l0gwPz3kxQBZrNYisw5YIr747jbQt9X W8j1/kB7ZHQOD3Fc/X+OdJgh/6DnLsv8Lkm5u5n1L3aHGXyP5cNSLdl2OcGyKMOk5K OPTVEyeWsduyMCGGKUBKg0jVayAqxmAcm5iA21sw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Zenghui Yu , Kalle Valo , Sasha Levin Subject: [PATCH 5.14 282/334] bcma: Fix memory leak for internally-handled cores Date: Mon, 13 Sep 2021 15:15:36 +0200 Message-Id: <20210913131122.961884464@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210913131113.390368911@linuxfoundation.org> References: <20210913131113.390368911@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Zenghui Yu [ Upstream commit b63aed3ff195130fef12e0af590f4838cf0201d8 ] kmemleak reported that dev_name() of internally-handled cores were leaked on driver unbinding. Let's use device_initialize() to take refcounts for them and put_device() to properly free the related stuff. While looking at it, there's another potential issue for those which should be *registered* into driver core. If device_register() failed, we put device once and freed bcma_device structures. In bcma_unregister_cores(), they're treated as unregistered and we hit both UAF and double-free. That smells not good and has also been fixed now. Fixes: ab54bc8460b5 ("bcma: fill core details for every device") Signed-off-by: Zenghui Yu Signed-off-by: Kalle Valo Link: https://lore.kernel.org/r/20210727025232.663-2-yuzenghui@huawei.com Signed-off-by: Sasha Levin --- drivers/bcma/main.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/bcma/main.c b/drivers/bcma/main.c index 6535614a7dc1..1df2b5801c3b 100644 --- a/drivers/bcma/main.c +++ b/drivers/bcma/main.c @@ -236,6 +236,7 @@ EXPORT_SYMBOL(bcma_core_irq); void bcma_prepare_core(struct bcma_bus *bus, struct bcma_device *core) { + device_initialize(&core->dev); core->dev.release = bcma_release_core_dev; core->dev.bus = &bcma_bus_type; dev_set_name(&core->dev, "bcma%d:%d", bus->num, core->core_index); @@ -277,11 +278,10 @@ static void bcma_register_core(struct bcma_bus *bus, struct bcma_device *core) { int err; - err = device_register(&core->dev); + err = device_add(&core->dev); if (err) { bcma_err(bus, "Could not register dev for core 0x%03X\n", core->id.id); - put_device(&core->dev); return; } core->dev_registered = true; @@ -372,7 +372,7 @@ void bcma_unregister_cores(struct bcma_bus *bus) /* Now noone uses internally-handled cores, we can free them */ list_for_each_entry_safe(core, tmp, &bus->cores, list) { list_del(&core->list); - kfree(core); + put_device(&core->dev); } } -- 2.30.2