From: Ayman Bagabas <ayman.bagabas@gmail.com>
To: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mattias Jacobsson <2pi@mok.nu>,
Dan Carpenter <dan.carpenter@oracle.com>,
kbuild test robot <lkp@intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: huawei-wmi: Fix a possible NULL deref
Date: Thu, 26 Dec 2019 15:42:05 -0500 [thread overview]
Message-ID: <20191226204205.qzfcmohulcfbcl4e@960> (raw)
In-Reply-To: <20191225235841.14393-1-ayman.bagabas@gmail.com>
Please ignore this patch I'll be sending another one. guid->guid_string
is always true.
On 19/12/25 06:58PM, Ayman Bagabas wrote:
> We're iterating over a NULL terminated array.
>
> Fixes: 1ac9abeb2e5b ("platform/x86: huawei-wmi: Move to platform driver")
> Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com>
> ---
> drivers/platform/x86/huawei-wmi.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/x86/huawei-wmi.c b/drivers/platform/x86/huawei-wmi.c
> index a2d846c4a7ee..42d461eeeff4 100644
> --- a/drivers/platform/x86/huawei-wmi.c
> +++ b/drivers/platform/x86/huawei-wmi.c
> @@ -784,13 +784,13 @@ static const struct wmi_device_id huawei_wmi_events_id_table[] = {
> static int huawei_wmi_probe(struct platform_device *pdev)
> {
> const struct wmi_device_id *guid = huawei_wmi_events_id_table;
> + struct input_dev *idev = *huawei_wmi->idev;
> int err;
>
> platform_set_drvdata(pdev, huawei_wmi);
> huawei_wmi->dev = &pdev->dev;
>
> - while (*guid->guid_string) {
> - struct input_dev *idev = *huawei_wmi->idev;
> + while (guid->guid_string) {
>
> if (wmi_has_guid(guid->guid_string)) {
> err = huawei_wmi_input_setup(&pdev->dev, guid->guid_string, &idev);
> @@ -820,7 +820,7 @@ static int huawei_wmi_remove(struct platform_device *pdev)
> {
> const struct wmi_device_id *guid = huawei_wmi_events_id_table;
>
> - while (*guid->guid_string) {
> + while (guid->guid_string) {
> if (wmi_has_guid(guid->guid_string))
> huawei_wmi_input_exit(&pdev->dev, guid->guid_string);
>
>
> base-commit: 46cf053efec6a3a5f343fead837777efe8252a46
> --
> 2.24.1
>
--
Thank you,
Ayman
next prev parent reply other threads:[~2019-12-26 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 23:58 [PATCH] platform/x86: huawei-wmi: Fix a possible NULL deref Ayman Bagabas
2019-12-26 20:42 ` Ayman Bagabas [this message]
2019-12-26 21:54 ` Dan Carpenter
2019-12-27 15:57 ` Ayman Bagabas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191226204205.qzfcmohulcfbcl4e@960 \
--to=ayman.bagabas@gmail.com \
--cc=2pi@mok.nu \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox