Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp4498668pxb; Thu, 14 Oct 2021 06:27:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwr8ITYpZ74rGG/Gx23FpY5vfI5HTcPrUmZNCWEXpErJbq2slnHKjS9YGevSV0V1Y0gm3p1 X-Received: by 2002:a62:1b92:0:b0:3eb:3f92:724 with SMTP id b140-20020a621b92000000b003eb3f920724mr5129080pfb.3.1634218077528; Thu, 14 Oct 2021 06:27:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634218077; cv=none; d=google.com; s=arc-20160816; b=FO+EVIdZiGcPAITrGX6TQj+o7DWBtmO5ML3VzPikkiS4GyjCiavpYWnJ7f8N9Mdohl 0Q1K93mdeBGKU+V/6VNHD1EySO74Gx1L5SwZ+7jlRE3KEvmDAUunzowUttcMSc9RnAnk lffYC8Cb5QCKG6Ijqh0Q4YSsFhYMh4wWZ2YlWwfUoNiwxuy3BLqQD1wQXILdfwYmZnnZ NN8obOogXSYWzJS1MbRurPKw2tHpDrkVyEcJ9IcG6+bITr3ZpiBIXUWVZY6ObdjZSVs4 HUT/KWgviF6qtKu513yXUFs/CryQ7PlxdkG2HI/MF3DghSCO73KGTMe84ibP1XxjFerT z8Wg== 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 :message-id:date:subject:cc:to:from; bh=P8aOv7UOLpsbmKwNPAd3F7JUfM196HeMA1VQ2fh6RT8=; b=Hc0GC+ot2aJTcq0PSWz5qBFFrIJ6vvNJcUg6bxRYBJwJuStAUNIX/gfgBDEwfVIE0P 1684PrJ56a5BJlHEty3s6kRaF7sjkiynAdoJ65FgHAazf/oC6b3z+ziHPlMWuZvGotk5 Ea2kF8UBYtsprPzHNEDTWim/t+SlK4wgF6g9OFg0nbdZUxd/rJM2BCXck8sNQ4vL2MtN HBK0OCW1a9yzG9+3EDvjkRfvyTEUltuOxmeQZIHr6aN/41ylB54GlW7+kkCx8SEv/nRf e9cE0Ux3Dkkdk9XgQtdgEMHS8rOO2bpwxFW/CaHfBWMjqqzZnQ9Zcincw81vZ/eAtbrO OTGA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z21si3899163pgv.590.2021.10.14.06.27.43; Thu, 14 Oct 2021 06:27:57 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231126AbhJNNXe (ORCPT + 99 others); Thu, 14 Oct 2021 09:23:34 -0400 Received: from szxga02-in.huawei.com ([45.249.212.188]:24313 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229637AbhJNNXd (ORCPT ); Thu, 14 Oct 2021 09:23:33 -0400 Received: from dggemv703-chm.china.huawei.com (unknown [172.30.72.53]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4HVVL1052GzYjTy; Thu, 14 Oct 2021 21:16:57 +0800 (CST) Received: from kwepemm600001.china.huawei.com (7.193.23.3) by dggemv703-chm.china.huawei.com (10.3.19.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 14 Oct 2021 21:21:26 +0800 Received: from huawei.com (10.175.104.82) by kwepemm600001.china.huawei.com (7.193.23.3) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Thu, 14 Oct 2021 21:21:25 +0800 From: Wang Hai To: , CC: , Subject: [PATCH] USB: serial: Fix possible memleak in keyspan_port_probe() Date: Thu, 14 Oct 2021 21:20:33 +0800 Message-ID: <20211014132033.554304-1-wanghai38@huawei.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.175.104.82] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To kwepemm600001.china.huawei.com (7.193.23.3) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I got memory leak as follows when doing fault injection test: unreferenced object 0xffff888258228440 (size 64): comm "kworker/7:2", pid 2005, jiffies 4294989509 (age 824.540s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] slab_post_alloc_hook+0x9c/0x490 [] kmem_cache_alloc_trace+0x1f7/0x470 [] keyspan_port_probe+0xa4/0x5d0 [keyspan] [] usb_serial_device_probe+0x97/0x1d0 [usbserial] [] really_probe+0x167/0x460 [] __driver_probe_device+0xf9/0x180 [] driver_probe_device+0x53/0x130 [] __device_attach_driver+0x105/0x130 [] bus_for_each_drv+0x129/0x190 [] __device_attach+0x1c9/0x270 [] device_initial_probe+0x20/0x30 [] bus_probe_device+0x142/0x160 [] device_add+0x829/0x1300 [] usb_serial_probe.cold+0xc9b/0x14ac [usbserial] [] usb_probe_interface+0x1aa/0x3c0 [usbcore] [] really_probe+0x167/0x460 If it fails to allocate memory for an out_buffer[i] or in_buffer[i], the previously allocated memory for out_buffer or in_buffer needs to be freed on the error handling path, otherwise a memory leak will result. Fixes: bad41a5bf177 ("USB: keyspan: fix port DMA-buffer allocations") Reported-by: Hulk Robot Signed-off-by: Wang Hai --- drivers/usb/serial/keyspan.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/usb/serial/keyspan.c b/drivers/usb/serial/keyspan.c index 87b89c99d517..ba27a9f0275b 100644 --- a/drivers/usb/serial/keyspan.c +++ b/drivers/usb/serial/keyspan.c @@ -2901,7 +2901,7 @@ static int keyspan_port_probe(struct usb_serial_port *port) p_priv->inack_buffer = kzalloc(INACK_BUFLEN, GFP_KERNEL); if (!p_priv->inack_buffer) - goto err_inack_buffer; + goto err_out_buffer; p_priv->outcont_buffer = kzalloc(OUTCONT_BUFLEN, GFP_KERNEL); if (!p_priv->outcont_buffer) @@ -2953,13 +2953,12 @@ static int keyspan_port_probe(struct usb_serial_port *port) err_outcont_buffer: kfree(p_priv->inack_buffer); -err_inack_buffer: +err_out_buffer: for (i = 0; i < ARRAY_SIZE(p_priv->out_buffer); ++i) kfree(p_priv->out_buffer[i]); -err_out_buffer: +err_in_buffer: for (i = 0; i < ARRAY_SIZE(p_priv->in_buffer); ++i) kfree(p_priv->in_buffer[i]); -err_in_buffer: kfree(p_priv); return -ENOMEM; -- 2.25.1