ACPICA: Refuse to evaluate a method if arguments are missing
[ Upstream commit 6fcab2791543924d438e7fa49276d0998b0a069f ] As reported in [1], a platform firmware update that increased the number of method parameters and forgot to update a least one of its callers, caused ACPICA to crash due to use-after-free. Since this a result of a clear AML issue that arguably cannot be fixed up by the interpreter (it cannot produce missing data out of thin air), address it by making ACPICA refuse to evaluate a method if the caller attempts to pass fewer arguments than expected to it. Closes: https://github.com/acpica/acpica/issues/1027 [1] Reported-by: Peter Williams <peter@newton.cx> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Reviewed-by: Hans de Goede <hansg@kernel.org> Tested-by: Hans de Goede <hansg@kernel.org> # Dell XPS 9640 with BIOS 1.12.0 Link: https://patch.msgid.link/5909446.DvuYhMxLoT@rjwysocki.net Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
347827bd0c
commit
d547779e72
@@ -483,6 +483,13 @@ acpi_ds_call_control_method(struct acpi_thread_state *thread,
|
|||||||
return_ACPI_STATUS(AE_NULL_OBJECT);
|
return_ACPI_STATUS(AE_NULL_OBJECT);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
if (this_walk_state->num_operands < obj_desc->method.param_count) {
|
||||||
|
ACPI_ERROR((AE_INFO, "Missing argument for method [%4.4s]",
|
||||||
|
acpi_ut_get_node_name(method_node)));
|
||||||
|
|
||||||
|
return_ACPI_STATUS(AE_AML_UNINITIALIZED_ARG);
|
||||||
|
}
|
||||||
|
|
||||||
/* Init for new method, possibly wait on method mutex */
|
/* Init for new method, possibly wait on method mutex */
|
||||||
|
|
||||||
status =
|
status =
|
||||||
|
Reference in New Issue
Block a user