8c2ae8
From 987a3b5cf7175916e2a4b6ea5b8e70f830dfe732 Mon Sep 17 00:00:00 2001
8c2ae8
From: Seunghun Han <kkamagui@gmail.com>
8c2ae8
Date: Wed, 19 Jul 2017 16:47:53 +0900
8c2ae8
Subject: [PATCH] acpi: acpica: fix acpi operand cache leak in dswstate.c
8c2ae8
8c2ae8
I found an ACPI cache leak in ACPI early termination and boot continuing case.
8c2ae8
8c2ae8
When early termination occurs due to malicious ACPI table, Linux kernel
8c2ae8
terminates ACPI function and continues to boot process. While kernel terminates
8c2ae8
ACPI function, kmem_cache_destroy() reports Acpi-Operand cache leak.
8c2ae8
8c2ae8
Boot log of ACPI operand cache leak is as follows:
8c2ae8
>[    0.585957] ACPI: Added _OSI(Module Device)
8c2ae8
>[    0.587218] ACPI: Added _OSI(Processor Device)
8c2ae8
>[    0.588530] ACPI: Added _OSI(3.0 _SCP Extensions)
8c2ae8
>[    0.589790] ACPI: Added _OSI(Processor Aggregator Device)
8c2ae8
>[    0.591534] ACPI Error: Illegal I/O port address/length above 64K: C806E00000004002/0x2 (20170303/hwvalid-155)
8c2ae8
>[    0.594351] ACPI Exception: AE_LIMIT, Unable to initialize fixed events (20170303/evevent-88)
8c2ae8
>[    0.597858] ACPI: Unable to start the ACPI Interpreter
8c2ae8
>[    0.599162] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)
8c2ae8
>[    0.601836] kmem_cache_destroy Acpi-Operand: Slab cache still has objects
8c2ae8
>[    0.603556] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc5 #26
8c2ae8
>[    0.605159] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
8c2ae8
>[    0.609177] Call Trace:
8c2ae8
>[    0.610063]  ? dump_stack+0x5c/0x81
8c2ae8
>[    0.611118]  ? kmem_cache_destroy+0x1aa/0x1c0
8c2ae8
>[    0.612632]  ? acpi_sleep_proc_init+0x27/0x27
8c2ae8
>[    0.613906]  ? acpi_os_delete_cache+0xa/0x10
8c2ae8
>[    0.617986]  ? acpi_ut_delete_caches+0x3f/0x7b
8c2ae8
>[    0.619293]  ? acpi_terminate+0xa/0x14
8c2ae8
>[    0.620394]  ? acpi_init+0x2af/0x34f
8c2ae8
>[    0.621616]  ? __class_create+0x4c/0x80
8c2ae8
>[    0.623412]  ? video_setup+0x7f/0x7f
8c2ae8
>[    0.624585]  ? acpi_sleep_proc_init+0x27/0x27
8c2ae8
>[    0.625861]  ? do_one_initcall+0x4e/0x1a0
8c2ae8
>[    0.627513]  ? kernel_init_freeable+0x19e/0x21f
8c2ae8
>[    0.628972]  ? rest_init+0x80/0x80
8c2ae8
>[    0.630043]  ? kernel_init+0xa/0x100
8c2ae8
>[    0.631084]  ? ret_from_fork+0x25/0x30
8c2ae8
>[    0.633343] vgaarb: loaded
8c2ae8
>[    0.635036] EDAC MC: Ver: 3.0.0
8c2ae8
>[    0.638601] PCI: Probing PCI hardware
8c2ae8
>[    0.639833] PCI host bridge to bus 0000:00
8c2ae8
>[    0.641031] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
8c2ae8
> ... Continue to boot and log is omitted ...
8c2ae8
8c2ae8
I analyzed this memory leak in detail and found acpi_ds_obj_stack_pop_and_
8c2ae8
delete() function miscalculated the top of the stack. acpi_ds_obj_stack_push()
8c2ae8
function uses walk_state->operand_index for start position of the top, but
8c2ae8
acpi_ds_obj_stack_pop_and_delete() function considers index 0 for it.
8c2ae8
Therefore, this causes acpi operand memory leak.
8c2ae8
8c2ae8
This cache leak causes a security threat because an old kernel (<= 4.9) shows
8c2ae8
memory locations of kernel functions in stack dump. Some malicious users
8c2ae8
could use this information to neutralize kernel ASLR.
8c2ae8
8c2ae8
I made a patch to fix ACPI operand cache leak.
8c2ae8
8c2ae8
Signed-off-by: Seunghun Han <kkamagui@gmail.com>
8c2ae8
8c2ae8
Github-Location: https://github.com/acpica/acpica/pull/295/commits/987a3b5cf7175916e2a4b6ea5b8e70f830dfe732
8c2ae8
---
8c2ae8
 source/components/dispatcher/dsutils.c | 9 ++++++++-
8c2ae8
 1 file changed, 8 insertions(+), 1 deletion(-)
8c2ae8
8c2ae8
Index: acpica-unix2-20180209/source/components/dispatcher/dsutils.c
8c2ae8
===================================================================
8c2ae8
--- acpica-unix2-20180209.orig/source/components/dispatcher/dsutils.c
8c2ae8
+++ acpica-unix2-20180209/source/components/dispatcher/dsutils.c
8c2ae8
@@ -761,6 +761,8 @@ AcpiDsCreateOperands (
8c2ae8
     ACPI_PARSE_OBJECT       *Arguments[ACPI_OBJ_NUM_OPERANDS];
8c2ae8
     UINT32                  ArgCount = 0;
8c2ae8
     UINT32                  Index = WalkState->NumOperands;
8c2ae8
+    UINT32                  PrevNumOperands = WalkState->NumOperands;
8c2ae8
+    UINT32                  NewNumOperands;
8c2ae8
     UINT32                  i;
8c2ae8
 
8c2ae8
 
8c2ae8
@@ -793,6 +795,7 @@ AcpiDsCreateOperands (
8c2ae8
 
8c2ae8
     /* Create the interpreter arguments, in reverse order */
8c2ae8
 
8c2ae8
+    NewNumOperands = Index;
8c2ae8
     Index--;
8c2ae8
     for (i = 0; i < ArgCount; i++)
8c2ae8
     {
8c2ae8
@@ -820,7 +823,11 @@ Cleanup:
8c2ae8
      * pop everything off of the operand stack and delete those
8c2ae8
      * objects
8c2ae8
      */
8c2ae8
-    AcpiDsObjStackPopAndDelete (ArgCount, WalkState);
8c2ae8
+    WalkState->NumOperands = i;
8c2ae8
+    AcpiDsObjStackPopAndDelete (NewNumOperands, WalkState);
8c2ae8
+
8c2ae8
+    /* Restore operand count */
8c2ae8
+    WalkState->NumOperands = PrevNumOperands;
8c2ae8
 
8c2ae8
     ACPI_EXCEPTION ((AE_INFO, Status, "While creating Arg %u", Index));
8c2ae8
     return_ACPI_STATUS (Status);