From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:29:25
When compiled with CONFIG_STRICT_KERNEL_RWX, the kernel must create
temporary mappings when patching itself. These mappings temporarily
override the strict RWX text protections to permit a write. Currently,
powerpc allocates a per-CPU VM area for patching. Patching occurs as
follows:
1. Map page of text to be patched to per-CPU VM area w/
PAGE_KERNEL protection
2. Patch text
3. Remove the temporary mapping
While the VM area is per-CPU, the mapping is actually inserted into the
kernel page tables. Presumably, this could allow another CPU to access
the normally write-protected text - either malicously or accidentally -
via this same mapping if the address of the VM area is known. Ideally,
the mapping should be kept local to the CPU doing the patching (or any
other sensitive operations requiring temporarily overriding memory
protections) [0].
x86 introduced "temporary mm" structs which allow the creation of
mappings local to a particular CPU [1]. This series intends to bring the
notion of a temporary mm to powerpc and harden powerpc by using such a
mapping for patching a kernel with strict RWX permissions.
The first patch introduces the temporary mm struct and API for powerpc
along with a new function to retrieve a current hw breakpoint.
The second patch uses the `poking_init` init hook added by the x86
patches to initialize a temporary mm and patching address. The patching
address is randomized between 0 and DEFAULT_MAP_WINDOW-PAGE_SIZE. The
upper limit is necessary due to how the hash MMU operates - by default
the space above DEFAULT_MAP_WINDOW is not available. For now, both hash
and radix randomize inside this range. The number of possible random
addresses is dependent on PAGE_SIZE and limited by DEFAULT_MAP_WINDOW.
Bits of entropy with 64K page size on BOOK3S_64:
bits of entropy = log2(DEFAULT_MAP_WINDOW_USER64 / PAGE_SIZE)
PAGE_SIZE=64K, DEFAULT_MAP_WINDOW_USER64=128TB
bits of entropy = log2(128TB / 64K)
bits of entropy = 31
Randomization occurs only once during initialization at boot.
The third patch replaces the VM area with the temporary mm in the
patching code. The page for patching has to be mapped PAGE_SHARED with
the hash MMU since hash prevents the kernel from accessing userspace
pages with PAGE_PRIVILEGED bit set. On the radix MMU the page is mapped with
PAGE_KERNEL which has the added benefit that we can skip KUAP.
The fourth and fifth patches implement an LKDTM test "proof-of-concept" which
exploits the previous vulnerability (ie. the mapping during patching is exposed
in kernel page tables and accessible by other CPUS). The LKDTM test is somewhat
"rough" in that it uses a brute-force approach - I am open to any suggestions
and/or ideas to improve this. Currently, the LKDTM test passes with this series
on POWER8 (hash) and POWER9 (radix, hash) and fails without this series (ie.
the temporary mapping for patching is exposed to CPUs other than the patching
CPU).
The test can be applied to a tree without this new series by applying
the last two patches of this series, and then fixing up in
/arch/powerpc/lib/code-patching.c:
#ifdef CONFIG_STRICT_KERNEL_RWX
static DEFINE_PER_CPU(struct vm_struct *, text_poke_area);
+#ifdef CONFIG_LKDTM
+unsigned long read_cpu_patching_addr(unsigned int cpu)
+{
+ return (unsigned long)(per_cpu(text_poke_area, cpu))->addr;
+}
+#endif
+
static int text_area_cpu_up(unsigned int cpu)
{
struct vm_struct *area;
I also have a tree with just linuxppc/next and the LKDTM test here:
https://github.com/cmr-informatik/linux/commits/percpu-lkdtm-only
Tested on Blackbird (8-core POWER9) w/ Hash (`disable_radix`) and Radix
MMUs.
v2: * Rebase on linuxppc/next:
commit 105fb38124a4 ("powerpc/8xx: Modify ptep_get()")
* Always dirty pte when mapping patch
* Use `ppc_inst_len` instead of `sizeof` on instructions
* Declare LKDTM patching addr accessor in header where it
belongs
v1: * Rebase on linuxppc/next (4336b9337824)
* Save and restore second hw watchpoint
* Use new ppc_inst_* functions for patching check and in LKDTM
test
rfc-v2: * Many fixes and improvements mostly based on extensive feedback and
testing by Christophe Leroy (thanks!).
* Make patching_mm and patching_addr static and mode '__ro_after_init'
to after the variable name (more common in other parts of the kernel)
* Use 'asm/debug.h' header instead of 'asm/hw_breakpoint.h' to fix
PPC64e compile
* Add comment explaining why we use BUG_ON() during the init call to
setup for patching later
* Move ptep into patch_mapping to avoid walking page tables a second
time when unmapping the temporary mapping
* Use KUAP under non-radix, also manually dirty the PTE for patch
mapping on non-BOOK3S_64 platforms
* Properly return any error from __patch_instruction
* Do not use 'memcmp' where a simple comparison is appropriate
* Simplify expression for patch address by removing pointer maths
* Add LKDTM test
[0]: https://github.com/linuxppc/issues/issues/224
[1]: https://lore.kernel.org/kernel-hardening/20190426232303.28381-1-nadav.amit@gmail.com/
Christopher M. Riedl (5):
powerpc/mm: Introduce temporary mm
powerpc/lib: Initialize a temporary mm for code patching
powerpc/lib: Use a temporary mm for code patching
powerpc/lib: Add LKDTM accessor for patching addr
powerpc: Add LKDTM test to hijack a patch mapping
arch/powerpc/include/asm/code-patching.h | 4 +
arch/powerpc/include/asm/debug.h | 1 +
arch/powerpc/include/asm/mmu_context.h | 64 +++++++++
arch/powerpc/kernel/process.c | 5 +
arch/powerpc/lib/code-patching.c | 176 +++++++++++------------
drivers/misc/lkdtm/core.c | 1 +
drivers/misc/lkdtm/lkdtm.h | 1 +
drivers/misc/lkdtm/perms.c | 99 +++++++++++++
8 files changed, 261 insertions(+), 90 deletions(-)
--
2.27.0
From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:26:01
When live patching a STRICT_RWX kernel, a mapping is installed at a
"patching address" with temporary write permissions. Provide a
LKDTM-only accessor function for this address in preparation for a LKDTM
test which attempts to "hijack" this mapping by writing to it from
another CPU.
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/include/asm/code-patching.h | 4 ++++
arch/powerpc/lib/code-patching.c | 7 +++++++
2 files changed, 11 insertions(+)
From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:27:42
x86 supports the notion of a temporary mm which restricts access to
temporary PTEs to a single CPU. A temporary mm is useful for situations
where a CPU needs to perform sensitive operations (such as patching a
STRICT_KERNEL_RWX kernel) requiring temporary mappings without exposing
said mappings to other CPUs. A side benefit is that other CPU TLBs do
not need to be flushed when the temporary mm is torn down.
Mappings in the temporary mm can be set in the userspace portion of the
address-space.
Interrupts must be disabled while the temporary mm is in use. HW
breakpoints, which may have been set by userspace as watchpoints on
addresses now within the temporary mm, are saved and disabled when
loading the temporary mm. The HW breakpoints are restored when unloading
the temporary mm. All HW breakpoints are indiscriminately disabled while
the temporary mm is in use.
Based on x86 implementation:
commit cefa929c034e
("x86/mm: Introduce temporary mm structs")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/include/asm/debug.h | 1 +
arch/powerpc/include/asm/mmu_context.h | 64 ++++++++++++++++++++++++++
arch/powerpc/kernel/process.c | 5 ++
3 files changed, 70 insertions(+)
From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:33:54
When live patching with STRICT_KERNEL_RWX, the CPU doing the patching
must use a temporary mapping which allows for writing to kernel text.
During the entire window of time when this temporary mapping is in use,
another CPU could write to the same mapping and maliciously alter kernel
text. Implement a LKDTM test to attempt to exploit such a openings when
a CPU is patching under STRICT_KERNEL_RWX. The test is only implemented
on powerpc for now.
The LKDTM "hijack" test works as follows:
1. A CPU executes an infinite loop to patch an instruction.
This is the "patching" CPU.
2. Another CPU attempts to write to the address of the temporary
mapping used by the "patching" CPU. This other CPU is the
"hijacker" CPU. The hijack either fails with a segfault or
succeeds, in which case some kernel text is now overwritten.
How to run the test:
mount -t debugfs none /sys/kernel/debug
(echo HIJACK_PATCH > /sys/kernel/debug/provoke-crash/DIRECT)
Signed-off-by: Christopher M. Riedl <redacted>
---
drivers/misc/lkdtm/core.c | 1 +
drivers/misc/lkdtm/lkdtm.h | 1 +
drivers/misc/lkdtm/perms.c | 99 ++++++++++++++++++++++++++++++++++++++
3 files changed, 101 insertions(+)
@@ -9,6 +9,7 @@#include<linux/vmalloc.h>#include<linux/mman.h>#include<linux/uaccess.h>+#include<linux/kthread.h>#include<asm/cacheflush.h>/* Whether or not to fill the target memory area with do_nothing(). */
@@ -213,6 +214,104 @@ void lkdtm_ACCESS_NULL(void)*ptr=tmp;}+#if defined(CONFIG_PPC) && defined(CONFIG_STRICT_KERNEL_RWX)+#include<include/asm/code-patching.h>++staticstructppc_inst*constpatch_site=(structppc_inst*)&do_nothing;++staticintlkdtm_patching_cpu(void*data)+{+interr=0;+structppc_instinsn=ppc_inst(0xdeadbeef);++pr_info("starting patching_cpu=%d\n",smp_processor_id());+do{+err=patch_instruction(patch_site,insn);+}while(ppc_inst_equal(ppc_inst_read(READ_ONCE(patch_site)),insn)&&+!err&&!kthread_should_stop());++if(err)+pr_warn("patch_instruction returned error: %d\n",err);++set_current_state(TASK_INTERRUPTIBLE);+while(!kthread_should_stop()){+schedule();+set_current_state(TASK_INTERRUPTIBLE);+}++returnerr;+}++voidlkdtm_HIJACK_PATCH(void)+{+structtask_struct*patching_kthrd;+structppc_instoriginal_insn;+intpatching_cpu,hijacker_cpu,attempts;+unsignedlongaddr;+boolhijacked;++if(num_online_cpus()<2){+pr_warn("need at least two cpus\n");+return;+}++original_insn=ppc_inst_read(READ_ONCE(patch_site));++hijacker_cpu=smp_processor_id();+patching_cpu=cpumask_any_but(cpu_online_mask,hijacker_cpu);++patching_kthrd=kthread_create_on_node(&lkdtm_patching_cpu,NULL,+cpu_to_node(patching_cpu),+"lkdtm_patching_cpu");+kthread_bind(patching_kthrd,patching_cpu);+wake_up_process(patching_kthrd);++addr=offset_in_page(patch_site)|read_cpu_patching_addr(patching_cpu);++pr_info("starting hijacker_cpu=%d\n",hijacker_cpu);+for(attempts=0;attempts<100000;++attempts){+/* Use __put_user to catch faults without an Oops */+hijacked=!__put_user(0xbad00bad,(unsignedint*)addr);++if(hijacked){+if(kthread_stop(patching_kthrd))+gotoout;+break;+}+}+pr_info("hijack attempts: %d\n",attempts);++if(hijacked){+if(*(unsignedint*)READ_ONCE(patch_site)==0xbad00bad)+pr_err("overwrote kernel text\n");+/*+*Therearewindowconditionswherethehijackercpumanagesto+*writetothepatchsitebutthesitegetsoverwrittenagainby+*thepatchingcpu.Westillconsiderthata"successful"hijack+*sincethehijackercpudidnotfaultonthewrite.+*/+pr_err("FAIL: wrote to another cpu's patching area\n");+}else{+kthread_stop(patching_kthrd);+}++out:+/* Restore the original insn for any future lkdtm tests */+patch_instruction(patch_site,original_insn);+}++#else++voidlkdtm_HIJACK_PATCH(void)+{+if(!IS_ENABLED(CONFIG_PPC))+pr_err("XFAIL: this test is powerpc-only\n");+if(!IS_ENABLED(CONFIG_STRICT_KERNEL_RWX))+pr_err("XFAIL: this test requires CONFIG_STRICT_KERNEL_RWX\n");+}++#endif /* CONFIG_PPC && CONFIG_STRICT_KERNEL_RWX */+void__initlkdtm_perms_init(void){/* Make sure we can write to __ro_after_init values during __init */
From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:35:47
Currently, code patching a STRICT_KERNEL_RWX exposes the temporary
mappings to other CPUs. These mappings should be kept local to the CPU
doing the patching. Use the pre-initialized temporary mm and patching
address for this purpose. Also add a check after patching to ensure the
patch succeeded.
Use the KUAP functions on non-BOOKS3_64 platforms since the temporary
mapping for patching uses a userspace address (to keep the mapping
local). On BOOKS3_64 platforms hash does not implement KUAP and on radix
the use of PAGE_KERNEL sets EAA[0] for the PTE which means the AMR
(KUAP) protection is ignored (see PowerISA v3.0b, Fig, 35).
Based on x86 implementation:
commit b3fd8e83ada0
("x86/alternatives: Use temporary mm for text poking")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 152 +++++++++++--------------------
1 file changed, 54 insertions(+), 98 deletions(-)
@@ -77,106 +78,57 @@ void __init poking_init(void)pte_unmap_unlock(ptep,ptl);}-staticDEFINE_PER_CPU(structvm_struct*,text_poke_area);--staticinttext_area_cpu_up(unsignedintcpu)-{-structvm_struct*area;--area=get_vm_area(PAGE_SIZE,VM_ALLOC);-if(!area){-WARN_ONCE(1,"Failed to create text area for cpu %d\n",-cpu);-return-1;-}-this_cpu_write(text_poke_area,area);--return0;-}--staticinttext_area_cpu_down(unsignedintcpu)-{-free_vm_area(this_cpu_read(text_poke_area));-return0;-}--/*-*Runasalateinitcall.Thisallowsalltheboottimepatchingtobedone-*simplybypatchingthecode,andthenwe'recalledherepriorto-*mark_rodata_ro(),whichhappensafterallinitcallsarerun.Although-*BUG_ON()isrude,inthiscaseitshouldonlyhappenifENOMEM,andwejudge-*itasbeingpreferabletoakernelthatwillcrashlaterwhensomeonetries-*tousepatch_instruction().-*/-staticint__initsetup_text_poke_area(void)-{-BUG_ON(!cpuhp_setup_state(CPUHP_AP_ONLINE_DYN,-"powerpc/text_poke:online",text_area_cpu_up,-text_area_cpu_down));--return0;-}-late_initcall(setup_text_poke_area);+structpatch_mapping{+spinlock_t*ptl;/* for protecting pte table */+pte_t*ptep;+structtemp_mmtemp_mm;+};/**Thiscanbecalledforkerneltextoramodule.*/-staticintmap_patch_area(void*addr,unsignedlongtext_poke_addr)+staticintmap_patch(constvoid*addr,structpatch_mapping*patch_mapping){-unsignedlongpfn;-interr;+structpage*page;+pte_tpte;+pgprot_tpgprot;if(is_vmalloc_addr(addr))-pfn=vmalloc_to_pfn(addr);+page=vmalloc_to_page(addr);else-pfn=__pa_symbol(addr)>>PAGE_SHIFT;+page=virt_to_page(addr);-err=map_kernel_page(text_poke_addr,(pfn<<PAGE_SHIFT),PAGE_KERNEL);+if(radix_enabled())+pgprot=PAGE_KERNEL;+else+pgprot=PAGE_SHARED;-pr_devel("Mapped addr %lx with pfn %lx:%d\n",text_poke_addr,pfn,err);-if(err)+patch_mapping->ptep=get_locked_pte(patching_mm,patching_addr,+&patch_mapping->ptl);+if(unlikely(!patch_mapping->ptep)){+pr_warn("map patch: failed to allocate pte for patching\n");return-1;+}++pte=mk_pte(page,pgprot);+pte=pte_mkdirty(pte);+set_pte_at(patching_mm,patching_addr,patch_mapping->ptep,pte);++init_temp_mm(&patch_mapping->temp_mm,patching_mm);+use_temporary_mm(&patch_mapping->temp_mm);return0;}-staticinlineintunmap_patch_area(unsignedlongaddr)+staticvoidunmap_patch(structpatch_mapping*patch_mapping){-pte_t*ptep;-pmd_t*pmdp;-pud_t*pudp;-p4d_t*p4dp;-pgd_t*pgdp;--pgdp=pgd_offset_k(addr);-if(unlikely(!pgdp))-return-EINVAL;--p4dp=p4d_offset(pgdp,addr);-if(unlikely(!p4dp))-return-EINVAL;--pudp=pud_offset(p4dp,addr);-if(unlikely(!pudp))-return-EINVAL;--pmdp=pmd_offset(pudp,addr);-if(unlikely(!pmdp))-return-EINVAL;--ptep=pte_offset_kernel(pmdp,addr);-if(unlikely(!ptep))-return-EINVAL;+/* In hash, pte_clear flushes the tlb */+pte_clear(patching_mm,patching_addr,patch_mapping->ptep);+unuse_temporary_mm(&patch_mapping->temp_mm);-pr_devel("clearing mm %p, pte %p, addr %lx\n",&init_mm,ptep,addr);--/*-*Inhash,pte_clearflushesthetlb,inradix,wehaveto-*/-pte_clear(&init_mm,addr,ptep);-flush_tlb_kernel_range(addr,addr+PAGE_SIZE);--return0;+/* In radix, we have to explicitly flush the tlb (no-op in hash) */+local_flush_tlb_mm(patching_mm);+pte_unmap_unlock(patch_mapping->ptep,patch_mapping->ptl);}staticintdo_patch_instruction(structppc_inst*addr,structppc_instinstr)
@@ -184,32 +136,36 @@ static int do_patch_instruction(struct ppc_inst *addr, struct ppc_inst instr)interr;structppc_inst*patch_addr=NULL;unsignedlongflags;-unsignedlongtext_poke_addr;-unsignedlongkaddr=(unsignedlong)addr;+structpatch_mappingpatch_mapping;/*-*Duringearlyearlybootpatch_instructioniscalled-*whentext_poke_areaisnotready,butwestillneed-*toallowpatching.Wejustdotheplainoldpatching+*Thepatching_mmisinitializedbeforecallingmark_rodata_ro.Prior+*tothis,patch_instructioniscalledwhenwedon'thave(anddon't+*need)thepatching_mmsojustdoplainoldpatching.*/-if(!this_cpu_read(text_poke_area))+if(!patching_mm)returnraw_patch_instruction(addr,instr);local_irq_save(flags);-text_poke_addr=(unsignedlong)__this_cpu_read(text_poke_area)->addr;-if(map_patch_area(addr,text_poke_addr)){-err=-1;+err=map_patch(addr,&patch_mapping);+if(err)gotoout;-}-patch_addr=(structppc_inst*)(text_poke_addr+(kaddr&~PAGE_MASK));+patch_addr=(structppc_inst*)(patching_addr|offset_in_page(addr));-__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+allow_write_to_user(patch_addr,ppc_inst_len(instr));+err=__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+prevent_write_to_user(patch_addr,ppc_inst_len(instr));-err=unmap_patch_area(text_poke_addr);-if(err)-pr_warn("failed to unmap %lx\n",text_poke_addr);+unmap_patch(&patch_mapping);+/*+*Somethingiswrongifwhatwejustwrotedoesn'tmatchwhatwe+*thinkwejustwrote.+*/+WARN_ON(!ppc_inst_equal(ppc_inst_read(addr),instr));out:local_irq_restore(flags);
From: Christopher M. Riedl <hidden> Date: 2020-07-09 04:37:18
When code patching a STRICT_KERNEL_RWX kernel the page containing the
address to be patched is temporarily mapped with permissive memory
protections. Currently, a per-cpu vmalloc patch area is used for this
purpose. While the patch area is per-cpu, the temporary page mapping is
inserted into the kernel page tables for the duration of the patching.
The mapping is exposed to CPUs other than the patching CPU - this is
undesirable from a hardening perspective.
Use the `poking_init` init hook to prepare a temporary mm and patching
address. Initialize the temporary mm by copying the init mm. Choose a
randomized patching address inside the temporary mm userspace address
portion. The next patch uses the temporary mm and patching address for
code patching.
Based on x86 implementation:
commit 4fc19708b165
("x86/alternatives: Initialize temporary mm for patching")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 33 ++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
Le 09/07/2020 à 06:03, Christopher M. Riedl a écrit :
Currently, code patching a STRICT_KERNEL_RWX exposes the temporary
mappings to other CPUs. These mappings should be kept local to the CPU
doing the patching. Use the pre-initialized temporary mm and patching
address for this purpose. Also add a check after patching to ensure the
patch succeeded.
While trying the LKDTM test, I realised that this is useless for non SMP.
Is it worth applying that change to non SMP systems ?
Christophe
quoted hunk
Use the KUAP functions on non-BOOKS3_64 platforms since the temporary
mapping for patching uses a userspace address (to keep the mapping
local). On BOOKS3_64 platforms hash does not implement KUAP and on radix
the use of PAGE_KERNEL sets EAA[0] for the PTE which means the AMR
(KUAP) protection is ignored (see PowerISA v3.0b, Fig, 35).
Based on x86 implementation:
commit b3fd8e83ada0
("x86/alternatives: Use temporary mm for text poking")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 152 +++++++++++--------------------
1 file changed, 54 insertions(+), 98 deletions(-)
@@ -77,106 +78,57 @@ void __init poking_init(void)pte_unmap_unlock(ptep,ptl);}-staticDEFINE_PER_CPU(structvm_struct*,text_poke_area);--staticinttext_area_cpu_up(unsignedintcpu)-{-structvm_struct*area;--area=get_vm_area(PAGE_SIZE,VM_ALLOC);-if(!area){-WARN_ONCE(1,"Failed to create text area for cpu %d\n",-cpu);-return-1;-}-this_cpu_write(text_poke_area,area);--return0;-}--staticinttext_area_cpu_down(unsignedintcpu)-{-free_vm_area(this_cpu_read(text_poke_area));-return0;-}--/*-*Runasalateinitcall.Thisallowsalltheboottimepatchingtobedone-*simplybypatchingthecode,andthenwe'recalledherepriorto-*mark_rodata_ro(),whichhappensafterallinitcallsarerun.Although-*BUG_ON()isrude,inthiscaseitshouldonlyhappenifENOMEM,andwejudge-*itasbeingpreferabletoakernelthatwillcrashlaterwhensomeonetries-*tousepatch_instruction().-*/-staticint__initsetup_text_poke_area(void)-{-BUG_ON(!cpuhp_setup_state(CPUHP_AP_ONLINE_DYN,-"powerpc/text_poke:online",text_area_cpu_up,-text_area_cpu_down));--return0;-}-late_initcall(setup_text_poke_area);+structpatch_mapping{+spinlock_t*ptl;/* for protecting pte table */+pte_t*ptep;+structtemp_mmtemp_mm;+};/**Thiscanbecalledforkerneltextoramodule.*/-staticintmap_patch_area(void*addr,unsignedlongtext_poke_addr)+staticintmap_patch(constvoid*addr,structpatch_mapping*patch_mapping){-unsignedlongpfn;-interr;+structpage*page;+pte_tpte;+pgprot_tpgprot;if(is_vmalloc_addr(addr))-pfn=vmalloc_to_pfn(addr);+page=vmalloc_to_page(addr);else-pfn=__pa_symbol(addr)>>PAGE_SHIFT;+page=virt_to_page(addr);-err=map_kernel_page(text_poke_addr,(pfn<<PAGE_SHIFT),PAGE_KERNEL);+if(radix_enabled())+pgprot=PAGE_KERNEL;+else+pgprot=PAGE_SHARED;-pr_devel("Mapped addr %lx with pfn %lx:%d\n",text_poke_addr,pfn,err);-if(err)+patch_mapping->ptep=get_locked_pte(patching_mm,patching_addr,+&patch_mapping->ptl);+if(unlikely(!patch_mapping->ptep)){+pr_warn("map patch: failed to allocate pte for patching\n");return-1;+}++pte=mk_pte(page,pgprot);+pte=pte_mkdirty(pte);+set_pte_at(patching_mm,patching_addr,patch_mapping->ptep,pte);++init_temp_mm(&patch_mapping->temp_mm,patching_mm);+use_temporary_mm(&patch_mapping->temp_mm);return0;}-staticinlineintunmap_patch_area(unsignedlongaddr)+staticvoidunmap_patch(structpatch_mapping*patch_mapping){-pte_t*ptep;-pmd_t*pmdp;-pud_t*pudp;-p4d_t*p4dp;-pgd_t*pgdp;--pgdp=pgd_offset_k(addr);-if(unlikely(!pgdp))-return-EINVAL;--p4dp=p4d_offset(pgdp,addr);-if(unlikely(!p4dp))-return-EINVAL;--pudp=pud_offset(p4dp,addr);-if(unlikely(!pudp))-return-EINVAL;--pmdp=pmd_offset(pudp,addr);-if(unlikely(!pmdp))-return-EINVAL;--ptep=pte_offset_kernel(pmdp,addr);-if(unlikely(!ptep))-return-EINVAL;+/* In hash, pte_clear flushes the tlb */+pte_clear(patching_mm,patching_addr,patch_mapping->ptep);+unuse_temporary_mm(&patch_mapping->temp_mm);-pr_devel("clearing mm %p, pte %p, addr %lx\n",&init_mm,ptep,addr);--/*-*Inhash,pte_clearflushesthetlb,inradix,wehaveto-*/-pte_clear(&init_mm,addr,ptep);-flush_tlb_kernel_range(addr,addr+PAGE_SIZE);--return0;+/* In radix, we have to explicitly flush the tlb (no-op in hash) */+local_flush_tlb_mm(patching_mm);+pte_unmap_unlock(patch_mapping->ptep,patch_mapping->ptl);}staticintdo_patch_instruction(structppc_inst*addr,structppc_instinstr)
@@ -184,32 +136,36 @@ static int do_patch_instruction(struct ppc_inst *addr, struct ppc_inst instr)interr;structppc_inst*patch_addr=NULL;unsignedlongflags;-unsignedlongtext_poke_addr;-unsignedlongkaddr=(unsignedlong)addr;+structpatch_mappingpatch_mapping;/*-*Duringearlyearlybootpatch_instructioniscalled-*whentext_poke_areaisnotready,butwestillneed-*toallowpatching.Wejustdotheplainoldpatching+*Thepatching_mmisinitializedbeforecallingmark_rodata_ro.Prior+*tothis,patch_instructioniscalledwhenwedon'thave(anddon't+*need)thepatching_mmsojustdoplainoldpatching.*/-if(!this_cpu_read(text_poke_area))+if(!patching_mm)returnraw_patch_instruction(addr,instr);local_irq_save(flags);-text_poke_addr=(unsignedlong)__this_cpu_read(text_poke_area)->addr;-if(map_patch_area(addr,text_poke_addr)){-err=-1;+err=map_patch(addr,&patch_mapping);+if(err)gotoout;-}-patch_addr=(structppc_inst*)(text_poke_addr+(kaddr&~PAGE_MASK));+patch_addr=(structppc_inst*)(patching_addr|offset_in_page(addr));-__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+allow_write_to_user(patch_addr,ppc_inst_len(instr));+err=__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+prevent_write_to_user(patch_addr,ppc_inst_len(instr));-err=unmap_patch_area(text_poke_addr);-if(err)-pr_warn("failed to unmap %lx\n",text_poke_addr);+unmap_patch(&patch_mapping);+/*+*Somethingiswrongifwhatwejustwrotedoesn'tmatchwhatwe+*thinkwejustwrote.+*/+WARN_ON(!ppc_inst_equal(ppc_inst_read(addr),instr));out:local_irq_restore(flags);
From: Christopher M. Riedl <hidden> Date: 2020-07-14 19:50:41
On Thu Jul 9, 2020 at 4:02 AM CDT, Christophe Leroy wrote:
Le 09/07/2020 à 06:03, Christopher M. Riedl a écrit :
quoted
Currently, code patching a STRICT_KERNEL_RWX exposes the temporary
mappings to other CPUs. These mappings should be kept local to the CPU
doing the patching. Use the pre-initialized temporary mm and patching
address for this purpose. Also add a check after patching to ensure the
patch succeeded.
While trying the LKDTM test, I realised that this is useless for non
SMP.
Is it worth applying that change to non SMP systems ?
Christophe
Hmm, I would say it's probably preferable to maintain a single
implementation of code-patching under STRICT_KERNEL_RWX instead of
two versions for SMP and non-SMP.
quoted
Use the KUAP functions on non-BOOKS3_64 platforms since the temporary
mapping for patching uses a userspace address (to keep the mapping
local). On BOOKS3_64 platforms hash does not implement KUAP and on radix
the use of PAGE_KERNEL sets EAA[0] for the PTE which means the AMR
(KUAP) protection is ignored (see PowerISA v3.0b, Fig, 35).
Based on x86 implementation:
commit b3fd8e83ada0
("x86/alternatives: Use temporary mm for text poking")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 152 +++++++++++--------------------
1 file changed, 54 insertions(+), 98 deletions(-)
@@ -77,106 +78,57 @@ void __init poking_init(void)pte_unmap_unlock(ptep,ptl);}-staticDEFINE_PER_CPU(structvm_struct*,text_poke_area);--staticinttext_area_cpu_up(unsignedintcpu)-{-structvm_struct*area;--area=get_vm_area(PAGE_SIZE,VM_ALLOC);-if(!area){-WARN_ONCE(1,"Failed to create text area for cpu %d\n",-cpu);-return-1;-}-this_cpu_write(text_poke_area,area);--return0;-}--staticinttext_area_cpu_down(unsignedintcpu)-{-free_vm_area(this_cpu_read(text_poke_area));-return0;-}--/*-*Runasalateinitcall.Thisallowsalltheboottimepatchingtobedone-*simplybypatchingthecode,andthenwe'recalledherepriorto-*mark_rodata_ro(),whichhappensafterallinitcallsarerun.Although-*BUG_ON()isrude,inthiscaseitshouldonlyhappenifENOMEM,andwejudge-*itasbeingpreferabletoakernelthatwillcrashlaterwhensomeonetries-*tousepatch_instruction().-*/-staticint__initsetup_text_poke_area(void)-{-BUG_ON(!cpuhp_setup_state(CPUHP_AP_ONLINE_DYN,-"powerpc/text_poke:online",text_area_cpu_up,-text_area_cpu_down));--return0;-}-late_initcall(setup_text_poke_area);+structpatch_mapping{+spinlock_t*ptl;/* for protecting pte table */+pte_t*ptep;+structtemp_mmtemp_mm;+};/**Thiscanbecalledforkerneltextoramodule.*/-staticintmap_patch_area(void*addr,unsignedlongtext_poke_addr)+staticintmap_patch(constvoid*addr,structpatch_mapping*patch_mapping){-unsignedlongpfn;-interr;+structpage*page;+pte_tpte;+pgprot_tpgprot;if(is_vmalloc_addr(addr))-pfn=vmalloc_to_pfn(addr);+page=vmalloc_to_page(addr);else-pfn=__pa_symbol(addr)>>PAGE_SHIFT;+page=virt_to_page(addr);-err=map_kernel_page(text_poke_addr,(pfn<<PAGE_SHIFT),PAGE_KERNEL);+if(radix_enabled())+pgprot=PAGE_KERNEL;+else+pgprot=PAGE_SHARED;-pr_devel("Mapped addr %lx with pfn %lx:%d\n",text_poke_addr,pfn,err);-if(err)+patch_mapping->ptep=get_locked_pte(patching_mm,patching_addr,+&patch_mapping->ptl);+if(unlikely(!patch_mapping->ptep)){+pr_warn("map patch: failed to allocate pte for patching\n");return-1;+}++pte=mk_pte(page,pgprot);+pte=pte_mkdirty(pte);+set_pte_at(patching_mm,patching_addr,patch_mapping->ptep,pte);++init_temp_mm(&patch_mapping->temp_mm,patching_mm);+use_temporary_mm(&patch_mapping->temp_mm);return0;}-staticinlineintunmap_patch_area(unsignedlongaddr)+staticvoidunmap_patch(structpatch_mapping*patch_mapping){-pte_t*ptep;-pmd_t*pmdp;-pud_t*pudp;-p4d_t*p4dp;-pgd_t*pgdp;--pgdp=pgd_offset_k(addr);-if(unlikely(!pgdp))-return-EINVAL;--p4dp=p4d_offset(pgdp,addr);-if(unlikely(!p4dp))-return-EINVAL;--pudp=pud_offset(p4dp,addr);-if(unlikely(!pudp))-return-EINVAL;--pmdp=pmd_offset(pudp,addr);-if(unlikely(!pmdp))-return-EINVAL;--ptep=pte_offset_kernel(pmdp,addr);-if(unlikely(!ptep))-return-EINVAL;+/* In hash, pte_clear flushes the tlb */+pte_clear(patching_mm,patching_addr,patch_mapping->ptep);+unuse_temporary_mm(&patch_mapping->temp_mm);-pr_devel("clearing mm %p, pte %p, addr %lx\n",&init_mm,ptep,addr);--/*-*Inhash,pte_clearflushesthetlb,inradix,wehaveto-*/-pte_clear(&init_mm,addr,ptep);-flush_tlb_kernel_range(addr,addr+PAGE_SIZE);--return0;+/* In radix, we have to explicitly flush the tlb (no-op in hash) */+local_flush_tlb_mm(patching_mm);+pte_unmap_unlock(patch_mapping->ptep,patch_mapping->ptl);}staticintdo_patch_instruction(structppc_inst*addr,structppc_instinstr)
@@ -184,32 +136,36 @@ static int do_patch_instruction(struct ppc_inst *addr, struct ppc_inst instr)interr;structppc_inst*patch_addr=NULL;unsignedlongflags;-unsignedlongtext_poke_addr;-unsignedlongkaddr=(unsignedlong)addr;+structpatch_mappingpatch_mapping;/*-*Duringearlyearlybootpatch_instructioniscalled-*whentext_poke_areaisnotready,butwestillneed-*toallowpatching.Wejustdotheplainoldpatching+*Thepatching_mmisinitializedbeforecallingmark_rodata_ro.Prior+*tothis,patch_instructioniscalledwhenwedon'thave(anddon't+*need)thepatching_mmsojustdoplainoldpatching.*/-if(!this_cpu_read(text_poke_area))+if(!patching_mm)returnraw_patch_instruction(addr,instr);local_irq_save(flags);-text_poke_addr=(unsignedlong)__this_cpu_read(text_poke_area)->addr;-if(map_patch_area(addr,text_poke_addr)){-err=-1;+err=map_patch(addr,&patch_mapping);+if(err)gotoout;-}-patch_addr=(structppc_inst*)(text_poke_addr+(kaddr&~PAGE_MASK));+patch_addr=(structppc_inst*)(patching_addr|offset_in_page(addr));-__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+allow_write_to_user(patch_addr,ppc_inst_len(instr));+err=__patch_instruction(addr,instr,patch_addr);+if(!radix_enabled())+prevent_write_to_user(patch_addr,ppc_inst_len(instr));-err=unmap_patch_area(text_poke_addr);-if(err)-pr_warn("failed to unmap %lx\n",text_poke_addr);+unmap_patch(&patch_mapping);+/*+*Somethingiswrongifwhatwejustwrotedoesn'tmatchwhatwe+*thinkwejustwrote.+*/+WARN_ON(!ppc_inst_equal(ppc_inst_read(addr),instr));out:local_irq_restore(flags);
On Wed, Jul 08, 2020 at 11:03:16PM -0500, Christopher M. Riedl wrote:
quoted hunk
When live patching with STRICT_KERNEL_RWX, the CPU doing the patching
must use a temporary mapping which allows for writing to kernel text.
During the entire window of time when this temporary mapping is in use,
another CPU could write to the same mapping and maliciously alter kernel
text. Implement a LKDTM test to attempt to exploit such a openings when
a CPU is patching under STRICT_KERNEL_RWX. The test is only implemented
on powerpc for now.
The LKDTM "hijack" test works as follows:
1. A CPU executes an infinite loop to patch an instruction.
This is the "patching" CPU.
2. Another CPU attempts to write to the address of the temporary
mapping used by the "patching" CPU. This other CPU is the
"hijacker" CPU. The hijack either fails with a segfault or
succeeds, in which case some kernel text is now overwritten.
How to run the test:
mount -t debugfs none /sys/kernel/debug
(echo HIJACK_PATCH > /sys/kernel/debug/provoke-crash/DIRECT)
Signed-off-by: Christopher M. Riedl <redacted>
---
drivers/misc/lkdtm/core.c | 1 +
drivers/misc/lkdtm/lkdtm.h | 1 +
drivers/misc/lkdtm/perms.c | 99 ++++++++++++++++++++++++++++++++++++++
3 files changed, 101 insertions(+)
@@ -9,6 +9,7 @@#include<linux/vmalloc.h>#include<linux/mman.h>#include<linux/uaccess.h>+#include<linux/kthread.h>#include<asm/cacheflush.h>/* Whether or not to fill the target memory area with do_nothing(). */
While this is probably fine, I'd prefer a new target instead of re-using
do_nothing.
+
+static int lkdtm_patching_cpu(void *data)
+{
+ int err = 0;
+ struct ppc_inst insn = ppc_inst(0xdeadbeef);
+
+ pr_info("starting patching_cpu=%d\n", smp_processor_id());
+ do {
+ err = patch_instruction(patch_site, insn);
+ } while (ppc_inst_equal(ppc_inst_read(READ_ONCE(patch_site)), insn) &&
+ !err && !kthread_should_stop());
+
+ if (err)
+ pr_warn("patch_instruction returned error: %d\n", err);
+
+ set_current_state(TASK_INTERRUPTIBLE);
+ while (!kthread_should_stop()) {
+ schedule();
+ set_current_state(TASK_INTERRUPTIBLE);
+ }
+
+ return err;
+}
+
+void lkdtm_HIJACK_PATCH(void)
+{
+ struct task_struct *patching_kthrd;
+ struct ppc_inst original_insn;
+ int patching_cpu, hijacker_cpu, attempts;
+ unsigned long addr;
+ bool hijacked;
+
+ if (num_online_cpus() < 2) {
+ pr_warn("need at least two cpus\n");
+ return;
+ }
+
+ original_insn = ppc_inst_read(READ_ONCE(patch_site));
+
+ hijacker_cpu = smp_processor_id();
+ patching_cpu = cpumask_any_but(cpu_online_mask, hijacker_cpu);
+
+ patching_kthrd = kthread_create_on_node(&lkdtm_patching_cpu, NULL,
+ cpu_to_node(patching_cpu),
+ "lkdtm_patching_cpu");
+ kthread_bind(patching_kthrd, patching_cpu);
+ wake_up_process(patching_kthrd);
+
+ addr = offset_in_page(patch_site) | read_cpu_patching_addr(patching_cpu);
+
+ pr_info("starting hijacker_cpu=%d\n", hijacker_cpu);
+ for (attempts = 0; attempts < 100000; ++attempts) {
+ /* Use __put_user to catch faults without an Oops */
+ hijacked = !__put_user(0xbad00bad, (unsigned int *)addr);
+
+ if (hijacked) {
+ if (kthread_stop(patching_kthrd))
+ goto out;
+ break;
+ }
+ }
+ pr_info("hijack attempts: %d\n", attempts);
+
+ if (hijacked) {
+ if (*(unsigned int *)READ_ONCE(patch_site) == 0xbad00bad)
+ pr_err("overwrote kernel text\n");
+ /*
+ * There are window conditions where the hijacker cpu manages to
+ * write to the patch site but the site gets overwritten again by
+ * the patching cpu. We still consider that a "successful" hijack
+ * since the hijacker cpu did not fault on the write.
+ */
+ pr_err("FAIL: wrote to another cpu's patching area\n");
+ } else {
+ kthread_stop(patching_kthrd);
+ }
+
+out:
+ /* Restore the original insn for any future lkdtm tests */
+ patch_instruction(patch_site, original_insn);
Can this test be done for x86's instruction patching too?
+}
+
+#else
+
+void lkdtm_HIJACK_PATCH(void)
+{
+ if (!IS_ENABLED(CONFIG_PPC))
+ pr_err("XFAIL: this test is powerpc-only\n");
+ if (!IS_ENABLED(CONFIG_STRICT_KERNEL_RWX))
+ pr_err("XFAIL: this test requires CONFIG_STRICT_KERNEL_RWX\n");
+}
+
+#endif /* CONFIG_PPC && CONFIG_STRICT_KERNEL_RWX */
+
void __init lkdtm_perms_init(void)
{
/* Make sure we can write to __ro_after_init values during __init */
--
2.27.0
arch/powerpc/lib/code-patching.c:53:13: warning: no previous prototype for function 'poking_init' [-Wmissing-prototypes]
void __init poking_init(void)
^
arch/powerpc/lib/code-patching.c:53:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void __init poking_init(void)
^
static
1 warning generated.
vim +/poking_init +53 arch/powerpc/lib/code-patching.c
52
> 53 void __init poking_init(void)
54 {
55 spinlock_t *ptl; /* for protecting pte table */
56 pte_t *ptep;
57
58 /*
59 * Some parts of the kernel (static keys for example) depend on
60 * successful code patching. Code patching under STRICT_KERNEL_RWX
61 * requires this setup - otherwise we cannot patch at all. We use
62 * BUG_ON() here and later since an early failure is preferred to
63 * buggy behavior and/or strange crashes later.
64 */
65 patching_mm = copy_init_mm();
66 BUG_ON(!patching_mm);
67
68 /*
69 * In hash we cannot go above DEFAULT_MAP_WINDOW easily.
70 * XXX: Do we want additional bits of entropy for radix?
71 */
72 patching_addr = (get_random_long() & PAGE_MASK) %
73 (DEFAULT_MAP_WINDOW - PAGE_SIZE);
74
75 ptep = get_locked_pte(patching_mm, patching_addr, &ptl);
76 BUG_ON(!ptep);
77 pte_unmap_unlock(ptep, ptl);
78 }
79
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
@@ -300,5 +301,68 @@ static inline int arch_dup_mmap(struct mm_struct *oldmm,return0;}+structtemp_mm{+structmm_struct*temp;+structmm_struct*prev;+boolis_kernel_thread;+structarch_hw_breakpointbrk[HBP_NUM_MAX];+};
This is on the nitpicky end, but I wonder if this should be named
temp_mm, or should be labelled something else to capture its broader
purpose as a context for code patching? I'm thinking that a store of
breakpoints is perhaps unusual in a memory-managment structure?
I don't have a better suggestion off the top of my head and I'm happy
for you to leave it, I just wanted to flag it as a possible way we could
be clearer.
You don't seem to restore active_mm below. I don't know what active_mm
does, so I don't know if this is a problem.
+ else
+ temp_mm->prev = current->mm;
+
+ /*
+ * Hash requires a non-NULL current->mm to allocate a userspace address
+ * when handling a page fault. Does not appear to hurt in Radix either.
+ */
+ current->mm = temp_mm->temp;
+ switch_mm_irqs_off(NULL, temp_mm->temp, current);
+
+ if (ppc_breakpoint_available()) {
I wondered if this could be changed during a text-patching operation.
AIUI, it potentially can on a P9 via "dawr_enable_dangerous" in debugfs.
I don't know if that's a problem. My concern is that you could turn off
breakpoints, call 'use_temporary_mm', then turn them back on again
before 'unuse_temporary_mm' and get a breakpoint while that can access
the temporary mm. Is there something else that makes that safe?
disabling IRQs maybe?
+ struct arch_hw_breakpoint null_brk = {0};
+ int i = 0;
+
+ for (; i < nr_wp_slots(); ++i) {
super nitpicky, and I'm not sure if this is actually documented, but I'd
usually see this written as:
for (i = 0; i < nr_wp_slots(); i++) {
Not sure if there's any reason that it _shouldn't_ be written the way
you've written it (and I do like initialising the variable when it's
defined!), I'm just not used to it. (Likewise with the unuse function.)
From: Daniel Axtens <hidden> Date: 2020-08-06 03:26:48
"Christopher M. Riedl" [off-list ref] writes:
quoted hunk
When code patching a STRICT_KERNEL_RWX kernel the page containing the
address to be patched is temporarily mapped with permissive memory
protections. Currently, a per-cpu vmalloc patch area is used for this
purpose. While the patch area is per-cpu, the temporary page mapping is
inserted into the kernel page tables for the duration of the patching.
The mapping is exposed to CPUs other than the patching CPU - this is
undesirable from a hardening perspective.
Use the `poking_init` init hook to prepare a temporary mm and patching
address. Initialize the temporary mm by copying the init mm. Choose a
randomized patching address inside the temporary mm userspace address
portion. The next patch uses the temporary mm and patching address for
code patching.
Based on x86 implementation:
commit 4fc19708b165
("x86/alternatives: Initialize temporary mm for patching")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 33 ++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
@@ -44,6 +46,37 @@ int raw_patch_instruction(struct ppc_inst *addr, struct ppc_inst instr)}#ifdef CONFIG_STRICT_KERNEL_RWX++staticstructmm_struct*patching_mm__ro_after_init;+staticunsignedlongpatching_addr__ro_after_init;++void__initpoking_init(void)+{+spinlock_t*ptl;/* for protecting pte table */+pte_t*ptep;++/*+*Somepartsofthekernel(statickeysforexample)dependon+*successfulcodepatching.CodepatchingunderSTRICT_KERNEL_RWX+*requiresthissetup-otherwisewecannotpatchatall.Weuse+*BUG_ON()hereandlatersinceanearlyfailureispreferredto+*buggybehaviorand/orstrangecrasheslater.+*/+patching_mm=copy_init_mm();+BUG_ON(!patching_mm);++/*+*InhashwecannotgoaboveDEFAULT_MAP_WINDOWeasily.+*XXX:Dowewantadditionalbitsofentropyforradix?+*/+patching_addr=(get_random_long()&PAGE_MASK)%+(DEFAULT_MAP_WINDOW-PAGE_SIZE);
It took me a while to understand this calculation. I see that it's
calculating a base address for a page in which to do patching. It does
the following:
- get a random long
- mask with PAGE_MASK so as to get a page aligned value
- make sure that the base address is at least one PAGE_SIZE below
DEFAULT_MAP_WINDOW so we have a clear page between the base and
DEFAULT_MAP_WINDOW.
On 64-bit Book3S with 64K pages, that works out to be
PAGE_SIZE = 0x0000 0000 0001 0000
PAGE_MASK = 0xFFFF FFFF FFFF 0000
DEFAULT_MAP_WINDOW = DEFAULT_MAP_WINDOW_USER64 = TASK_SIZE_128TB
= 0x0000_8000_0000_0000
DEFAULT_MAP_WINDOW - PAGE_SIZE = 0x0000 7FFF FFFF 0000
It took a while (and a conversation with my wife who studied pure
maths!) but I am convinced that the modulo preserves the page-alignement
of the patching address.
One thing I did realise is that patching_addr can be zero at the end of
this process. That seems dubious and slightly error-prone to me - is
the patching process robust to that or should we exclude it?
Anyway, if I have the maths right, that there are 0x7fffffff or ~2
billion possible locations for the patching page, which is just shy of
31 bits of entropy.
I think this compares pretty favourably to most (K)ASLR implementations?
What's the range if built with 4k pages?
Kind regards,
Daniel
From: Christopher M. Riedl <hidden> Date: 2020-08-17 03:07:18
On Thu Aug 6, 2020 at 8:24 AM CDT, Daniel Axtens wrote:
"Christopher M. Riedl" [off-list ref] writes:
quoted
When code patching a STRICT_KERNEL_RWX kernel the page containing the
address to be patched is temporarily mapped with permissive memory
protections. Currently, a per-cpu vmalloc patch area is used for this
purpose. While the patch area is per-cpu, the temporary page mapping is
inserted into the kernel page tables for the duration of the patching.
The mapping is exposed to CPUs other than the patching CPU - this is
undesirable from a hardening perspective.
Use the `poking_init` init hook to prepare a temporary mm and patching
address. Initialize the temporary mm by copying the init mm. Choose a
randomized patching address inside the temporary mm userspace address
portion. The next patch uses the temporary mm and patching address for
code patching.
Based on x86 implementation:
commit 4fc19708b165
("x86/alternatives: Initialize temporary mm for patching")
Signed-off-by: Christopher M. Riedl <redacted>
---
arch/powerpc/lib/code-patching.c | 33 ++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
@@ -44,6 +46,37 @@ int raw_patch_instruction(struct ppc_inst *addr, struct ppc_inst instr)}#ifdef CONFIG_STRICT_KERNEL_RWX++staticstructmm_struct*patching_mm__ro_after_init;+staticunsignedlongpatching_addr__ro_after_init;++void__initpoking_init(void)+{+spinlock_t*ptl;/* for protecting pte table */+pte_t*ptep;++/*+*Somepartsofthekernel(statickeysforexample)dependon+*successfulcodepatching.CodepatchingunderSTRICT_KERNEL_RWX+*requiresthissetup-otherwisewecannotpatchatall.Weuse+*BUG_ON()hereandlatersinceanearlyfailureispreferredto+*buggybehaviorand/orstrangecrasheslater.+*/+patching_mm=copy_init_mm();+BUG_ON(!patching_mm);++/*+*InhashwecannotgoaboveDEFAULT_MAP_WINDOWeasily.+*XXX:Dowewantadditionalbitsofentropyforradix?+*/+patching_addr=(get_random_long()&PAGE_MASK)%+(DEFAULT_MAP_WINDOW-PAGE_SIZE);
It took me a while to understand this calculation. I see that it's
calculating a base address for a page in which to do patching. It does
the following:
I will add a comment explaining the calulcation in the next spin.
- get a random long
- mask with PAGE_MASK so as to get a page aligned value
- make sure that the base address is at least one PAGE_SIZE below
DEFAULT_MAP_WINDOW so we have a clear page between the base and
DEFAULT_MAP_WINDOW.
On 64-bit Book3S with 64K pages, that works out to be
PAGE_SIZE = 0x0000 0000 0001 0000
PAGE_MASK = 0xFFFF FFFF FFFF 0000
DEFAULT_MAP_WINDOW = DEFAULT_MAP_WINDOW_USER64 = TASK_SIZE_128TB
= 0x0000_8000_0000_0000
DEFAULT_MAP_WINDOW - PAGE_SIZE = 0x0000 7FFF FFFF 0000
It took a while (and a conversation with my wife who studied pure
maths!) but I am convinced that the modulo preserves the page-alignement
of the patching address.
I am glad a proper mathematician agrees because my maths are decidedly
unpure :)
One thing I did realise is that patching_addr can be zero at the end of
this process. That seems dubious and slightly error-prone to me - is
the patching process robust to that or should we exclude it?
Good catch! I will fix this in the next spin.
Anyway, if I have the maths right, that there are 0x7fffffff or ~2
billion possible locations for the patching page, which is just shy of
31 bits of entropy.
I think this compares pretty favourably to most (K)ASLR implementations?
Using the formula from my series coverletter, we should expect 34 bits
of entropy since DEFAULT_MAP_WINDOW_USER64 is 64TB for 4K pages:
bits of entropy = log2(DEFAULT_MAP_WINDOW_USER64 / PAGE_SIZE)
PAGE_SIZE=4K, DEFAULT_MAP_WINDOW_USER64=64TB
bits of entropy = log2(64TB / 4K)
bits of entropy = 34
@@ -300,5 +301,68 @@ static inline int arch_dup_mmap(struct mm_struct *oldmm,return0;}+structtemp_mm{+structmm_struct*temp;+structmm_struct*prev;+boolis_kernel_thread;+structarch_hw_breakpointbrk[HBP_NUM_MAX];+};
This is on the nitpicky end, but I wonder if this should be named
temp_mm, or should be labelled something else to capture its broader
purpose as a context for code patching? I'm thinking that a store of
breakpoints is perhaps unusual in a memory-managment structure?
I don't have a better suggestion off the top of my head and I'm happy
for you to leave it, I just wanted to flag it as a possible way we could
be clearer.
First of all thank you for the review!
I had actually planned to move all this code into lib/code-patching.c
directly (and it turns out that's what x86 ended up doing as well).
You don't seem to restore active_mm below. I don't know what active_mm
does, so I don't know if this is a problem.
For kernel threads 'current->mm' is NULL since a kthread does not need
a userspace mm; however they still need a mm so they "borrow" one which
is indicated by 'current->active_mm'.
'current->mm' needs to be restored because Hash requires a non-NULL
value when handling a page fault and so 'current->mm' gets set to the
temp_mm. This is a special case for kernel threads and Hash translation.
quoted
+ else
+ temp_mm->prev = current->mm;
+
+ /*
+ * Hash requires a non-NULL current->mm to allocate a userspace address
+ * when handling a page fault. Does not appear to hurt in Radix either.
+ */
+ current->mm = temp_mm->temp;
+ switch_mm_irqs_off(NULL, temp_mm->temp, current);
+
+ if (ppc_breakpoint_available()) {
I wondered if this could be changed during a text-patching operation.
AIUI, it potentially can on a P9 via "dawr_enable_dangerous" in debugfs.
I don't know if that's a problem. My concern is that you could turn off
breakpoints, call 'use_temporary_mm', then turn them back on again
before 'unuse_temporary_mm' and get a breakpoint while that can access
the temporary mm. Is there something else that makes that safe?
disabling IRQs maybe?
Hmm, I will have to investigate this more. I'm not sure if there is a
better way to just completely disable breakpoints while the temporary mm
is in use.
quoted
+ struct arch_hw_breakpoint null_brk = {0};
+ int i = 0;
+
+ for (; i < nr_wp_slots(); ++i) {
super nitpicky, and I'm not sure if this is actually documented, but I'd
usually see this written as:
for (i = 0; i < nr_wp_slots(); i++) {
Not sure if there's any reason that it _shouldn't_ be written the way
you've written it (and I do like initialising the variable when it's
defined!), I'm just not used to it. (Likewise with the unuse function.)
I've found other places (even in arch/powerpc!) where this is done so I
think it's fine. I prefer using this style when the variable
declaration and initialization are "close" to the loop statement.