lkml.org 
[lkml]   [2016]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Subject[RFC][PATCH 0/3] Sanitization of buddy pages
    Date
    Hi,

    This is an implementation of page poisoning/sanitization for all arches. It
    takes advantage of the existing implementation for
    !ARCH_SUPPORTS_DEBUG_PAGEALLOC arches. This is a different approach than what
    the Grsecurity patches were taking but should provide equivalent functionality.

    For those who aren't familiar with this, the goal of sanitization is to reduce
    the severity of use after free and uninitialized data bugs. Memory is cleared
    on free so any sensitive data is no longer available. Discussion of
    sanitization was brough up in a thread about CVEs
    (lkml.kernel.org/g/<20160119112812.GA10818@mwanda>)

    I eventually expect Kconfig names will want to be changed and or moved if this
    is going to be used for security but that can happen later.

    Credit to Mathias Krause for the version in grsecurity

    Laura Abbott (3):
    mm/debug-pagealloc.c: Split out page poisoning from debug page_alloc
    mm/page_poison.c: Enable PAGE_POISONING as a separate option
    mm/page_poisoning.c: Allow for zero poisoning

    Documentation/kernel-parameters.txt | 5 ++
    include/linux/mm.h | 13 +++
    include/linux/poison.h | 4 +
    mm/Kconfig.debug | 35 +++++++-
    mm/Makefile | 5 +-
    mm/debug-pagealloc.c | 127 +----------------------------
    mm/page_alloc.c | 10 ++-
    mm/page_poison.c | 158 ++++++++++++++++++++++++++++++++++++
    8 files changed, 228 insertions(+), 129 deletions(-)
    create mode 100644 mm/page_poison.c

    --
    2.5.0

    \
     
     \ /
      Last update: 2016-01-25 18:41    [W:2.911 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site