public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Zhongjin <chenzhongjin@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Bob Moore <robert.moore@intel.com>
Subject: Re: [PATCH] ACPICA: Fix error code path in acpi_ds_call_control_method()
Date: Tue, 8 Nov 2022 09:16:19 +0800	[thread overview]
Message-ID: <0f37ecd9-7859-ea41-80e2-9d4297f69b3d@huawei.com> (raw)
In-Reply-To: <2669303.mvXUDI8C0e@kreacher>

On 2022/11/8 1:42, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> A use-after-free in acpi_ps_parse_aml() after a failing invocaion of
> acpi_ds_call_control_method() is reported by KASAN [1] and code
> inspection reveals that next_walk_state pushed to the thread by
> acpi_ds_create_walk_state() is freed on errors, but it is not popped
> from the thread beforehand.  Thus acpi_ds_get_current_walk_state()
> called by acpi_ps_parse_aml() subsequently returns it as the new
> walk state which is incorrect.
>
> To address this, make acpi_ds_call_control_method() call
> acpi_ds_pop_walk_state() to pop next_walk_state from the thread before
> returning an error.
>
> Link: https://lore.kernel.org/linux-acpi/20221019073443.248215-1-chenzhongjin@huawei.com/
> Reported-by: Chen Zhongjin <chenzhongjin@huawei.com>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>   drivers/acpi/acpica/dsmethod.c |   10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
>
> Index: linux-pm/drivers/acpi/acpica/dsmethod.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/acpica/dsmethod.c
> +++ linux-pm/drivers/acpi/acpica/dsmethod.c
> @@ -517,7 +517,7 @@ acpi_ds_call_control_method(struct acpi_
>   	info = ACPI_ALLOCATE_ZEROED(sizeof(struct acpi_evaluate_info));
>   	if (!info) {
>   		status = AE_NO_MEMORY;
> -		goto cleanup;
> +		goto pop_walk_state;
>   	}
>   
>   	info->parameters = &this_walk_state->operands[0];
> @@ -529,7 +529,7 @@ acpi_ds_call_control_method(struct acpi_
>   
>   	ACPI_FREE(info);
>   	if (ACPI_FAILURE(status)) {
> -		goto cleanup;
> +		goto pop_walk_state;
>   	}
>   
>   	next_walk_state->method_nesting_depth =
> @@ -575,6 +575,12 @@ acpi_ds_call_control_method(struct acpi_
>   
>   	return_ACPI_STATUS(status);
>   
> +pop_walk_state:
> +
> +	/* On error, pop the walk state to be deleted from thread */
> +
> +	acpi_ds_pop_walk_state(thread);
> +
>   cleanup:
>   
>   	/* On error, we must terminate the method properly */
>
>
LGTM

Reviewed-by: Chen Zhongjin <chenzhongjin@huawei.com>


      reply	other threads:[~2022-11-08  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 17:42 [PATCH] ACPICA: Fix error code path in acpi_ds_call_control_method() Rafael J. Wysocki
2022-11-08  1:16 ` Chen Zhongjin [this message]

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=0f37ecd9-7859-ea41-80e2-9d4297f69b3d@huawei.com \
    --to=chenzhongjin@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robert.moore@intel.com \
    /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