From: Yang Yingliang <yangyingliang@huawei.com>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <lvjianmin@loongson.cn>,
<chenhuacai@loongson.cn>
Subject: Re: [PATCH] platform/loongarch: laptop: fix possible UAF in generic_acpi_laptop_init()
Date: Fri, 14 Oct 2022 09:23:03 +0800 [thread overview]
Message-ID: <b2dcb989-4bda-8921-a5a0-7ea29d6382ad@huawei.com> (raw)
In-Reply-To: <CAAhV-H48bH5VAYhsMvupUSWouAUR=s9b4hJYdJYdymCYbKQfjA@mail.gmail.com>
Hi, Huacai
On 2022/10/13 23:47, Huacai Chen wrote:
> Hi, Yingliang,
>
> Thank you for your patches, but could you please merge the two trivial
> patches to a single one?
It's OK to merge them into a single one in v2.
But the two patches solved different things, they are not relative.
Thanks,
Yang
>
> Huacai
>
> On Thu, Oct 13, 2022 at 9:12 PM Yang Yingliang <yangyingliang@huawei.com> wrote:
>> Current the return value of 'sub_driver->init' is not checked,
>> if sparse_keymap_setup() called in the init function fails,
>> 'generic_inputdev' is freed, then it willl lead a UAF when
>> using it in generic_acpi_laptop_init(). Fix it by checking
>> return value. Set generic_inputdev to NULL after free to avoid
>> double free it.
>>
>> Fixes: 6246ed09111f ("LoongArch: Add ACPI-based generic laptop driver")
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>> drivers/platform/loongarch/loongson-laptop.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/platform/loongarch/loongson-laptop.c b/drivers/platform/loongarch/loongson-laptop.c
>> index f0166ad5d2c2..a665fd1042ac 100644
>> --- a/drivers/platform/loongarch/loongson-laptop.c
>> +++ b/drivers/platform/loongarch/loongson-laptop.c
>> @@ -448,6 +448,7 @@ static int __init event_init(struct generic_sub_driver *sub_driver)
>> if (ret < 0) {
>> pr_err("Failed to setup input device keymap\n");
>> input_free_device(generic_inputdev);
>> + generic_inputdev = NULL;
>>
>> return ret;
>> }
>> @@ -502,8 +503,11 @@ static int __init generic_subdriver_init(struct generic_sub_driver *sub_driver)
>> if (ret)
>> return -EINVAL;
>>
>> - if (sub_driver->init)
>> - sub_driver->init(sub_driver);
>> + if (sub_driver->init) {
>> + ret = sub_driver->init(sub_driver);
>> + if (ret)
>> + goto err_out;
>> + }
>>
>> if (sub_driver->notify) {
>> ret = setup_acpi_notify(sub_driver);
>> --
>> 2.25.1
>>
> .
next prev parent reply other threads:[~2022-10-14 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 13:12 Yang Yingliang
2022-10-13 15:47 ` Huacai Chen
2022-10-14 1:23 ` Yang Yingliang [this message]
2022-10-14 1:32 ` Huacai Chen
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=b2dcb989-4bda-8921-a5a0-7ea29d6382ad@huawei.com \
--to=yangyingliang@huawei.com \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
/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
all inboxes | Powered by JetHome®