[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180920052204.GA15695@kroah.com>
Date: Thu, 20 Sep 2018 07:22:04 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: "Luis R. Rodriguez" <mcgrof@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
stable@...r.kernel.org, Rishabh Bhatnagar <rishabhb@...eaurora.org>
Subject: Re: [PATCH] firmware: Always initialize the fw_priv list object
On Wed, Sep 19, 2018 at 06:09:38PM -0700, Bjorn Andersson wrote:
> When freeing the fw_priv the item is taken off the list. This causes an
> oops in the FW_OPT_NOCACHE case as the list object is not initialized.
>
> Make sure to initialize the list object regardless of this flag.
>
> Fixes: 422b3db2a503 ("firmware: Fix security issue with request_firmware_into_buf()")
> Cc: stable@...r.kernel.org
> Cc: Rishabh Bhatnagar <rishabhb@...eaurora.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@...aro.org>
> ---
> drivers/base/firmware_loader/main.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Is this being triggered by some hardware somewhere today? Or is this
just a fix found by code inspection?
thanks,
greg k-h
Powered by blists - more mailing lists