[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrHYZb2BT8fQMcaR@hovoldconsulting.com>
Date: Tue, 21 Jun 2022 16:40:37 +0200
From: Johan Hovold <johan@...nel.org>
To: Dongliang Mu <mudongliangabcd@...il.com>
Cc: vireshk@...nel.org, elder@...nel.org,
Greg KH <gregkh@...uxfoundation.org>,
greybus-dev@...ts.linaro.org, linux-staging@...ts.linux.dev,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Unitialized Variable and Null Pointer Dereference bug in
gb_bootrom_get_firmware
On Tue, Jun 21, 2022 at 10:36:04PM +0800, Dongliang Mu wrote:
> Hi maintainers,
>
> I would like to send one bug report.
>
> In gb_bootrom_get_firmware, if the first branch is satisfied, it will
> go to queue_work, leading to the dereference of uninitialized const
> variable "fw". If the second branch is satisfied, it will go to unlock
> with fw as NULL pointer, leading to a NULL Pointer Dereference.
This sounds like the false positive that checkers keep tripping over.
Please double check your analysis and search the archives first.
Johan
Powered by blists - more mailing lists