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