Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1013725yba; Thu, 4 Apr 2019 02:26:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqyZnc5PfLa07cJp+x6W2+JDvjz4REnTZEouW2zuyAEJFzZl7CQLJMf96iR3pyPgKy1K3Mt3 X-Received: by 2002:a17:902:9043:: with SMTP id w3mr5286482plz.101.1554369983960; Thu, 04 Apr 2019 02:26:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554369983; cv=none; d=google.com; s=arc-20160816; b=lyJ9K7L5jtJlDglyty4v5fNViPORpY7W81CujKDrZOK1U0TVl7ZKKl80EekHZSF9eX YRC1MuTriA+CwZEn7P9sdPjeaHzzwbB8YGIoOtwSCMiaV0TIzfxUL0Trw3WzLbVKgcsS qg96e+4KHdx8EG8oVW2X1ibLmfI5vOtpxtklkSJ/VU1c6oxE5zqbbCz9z/9jlX70mj/x Alyx7Oaf9Z9lVvdVh/1lBYSKpB9v/gYyP0c3TkXYQfljuas57EsoIVWpOVBU/wxYPqk0 lwTdo9Zdkiq8yeZP5qxvHG1TjgQ9jXlIoQVENC7Gth73ii58CjWm06Iv0Yfh8zv5C5+u ukIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=FJsnFvYjADztWCCla44oY/sZVwXmxVuM8XibKazs3Ww=; b=n5u6opgpgI6iz4zinnafLdgGCSIMbzoHoSh9s9hVo3vpwD/E/H4He4zbeBLS2iK1Y5 pIjU6i9WDgeV4Ro2mmX0ZlkUWa6Q0gKpHen/YWkejU2U1d7vadGpe271y4H6fI8efSzj C767JXbqRsgVCboasbPgL7hXxSyG/K8DDjxS/fSLuWEQyo2J5hmlHAp88qv+o/BVolh9 tRmFKm0TgsAoZyFATK5qUSXRgbmjETIBoCr8mAOLpnCut0/tAEod1Nz5l5b8263dzou4 uvuXvDa65eZSa8IVas7FRNz+4ojy8Q1LIHle0T6JUBH520EoORAFdntHu+ZQjMvg+Ut+ Ri0g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=I3zYkw2p; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k3si16492147pfb.100.2019.04.04.02.26.08; Thu, 04 Apr 2019 02:26:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=I3zYkw2p; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387681AbfDDJZe (ORCPT + 99 others); Thu, 4 Apr 2019 05:25:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:54152 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387606AbfDDJNo (ORCPT ); Thu, 4 Apr 2019 05:13:44 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 727B32054F; Thu, 4 Apr 2019 09:13:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554369223; bh=3lEUaMx08+EmfueR731CUts/sZ0UEIYFJD6fGpWp7mI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=I3zYkw2pcHGNgEwBAeWv5/s+oH4703LpiBM4ludUFQVCVnO0t9cy1jCy7PLhN7OLD aps+i6fO4BUwzuZqE9j7jV8LNNT30PiZ9B2oeR96piNA1KWipBlfYQGAjYVPN7BDaY n7Bo80y2o9hD6VMMA+OX6MA1GTGXlz2WiSmu5IOc= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Michal Kazior , Jacek Anaszewski , Sasha Levin Subject: [PATCH 5.0 130/246] leds: lp55xx: fix null deref on firmware load failure Date: Thu, 4 Apr 2019 10:47:10 +0200 Message-Id: <20190404084623.709192201@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190404084619.236418459@linuxfoundation.org> References: <20190404084619.236418459@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 5.0-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit 5ddb0869bfc1bca6cfc592c74c64a026f936638c ] I've stumbled upon a kernel crash and the logs pointed me towards the lp5562 driver: > <4>[306013.841294] lp5562 0-0030: Direct firmware load for lp5562 failed with error -2 > <4>[306013.894990] lp5562 0-0030: Falling back to user helper > ... > <3>[306073.924886] lp5562 0-0030: firmware request failed > <1>[306073.939456] Unable to handle kernel NULL pointer dereference at virtual address 00000000 > <4>[306074.251011] PC is at _raw_spin_lock+0x1c/0x58 > <4>[306074.255539] LR is at release_firmware+0x6c/0x138 > ... After taking a look I noticed firmware_release() could be called with either NULL or a dangling pointer. Fixes: 10c06d178df11 ("leds-lp55xx: support firmware interface") Signed-off-by: Michal Kazior Signed-off-by: Jacek Anaszewski Signed-off-by: Sasha Levin --- drivers/leds/leds-lp55xx-common.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/leds/leds-lp55xx-common.c b/drivers/leds/leds-lp55xx-common.c index 3d79a6380761..723f2f17497a 100644 --- a/drivers/leds/leds-lp55xx-common.c +++ b/drivers/leds/leds-lp55xx-common.c @@ -201,7 +201,7 @@ static void lp55xx_firmware_loaded(const struct firmware *fw, void *context) if (!fw) { dev_err(dev, "firmware request failed\n"); - goto out; + return; } /* handling firmware data is chip dependent */ @@ -214,9 +214,9 @@ static void lp55xx_firmware_loaded(const struct firmware *fw, void *context) mutex_unlock(&chip->lock); -out: /* firmware should be released for other channel use */ release_firmware(chip->fw); + chip->fw = NULL; } static int lp55xx_request_firmware(struct lp55xx_chip *chip) -- 2.19.1