public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen@linux.intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	hpa@zytor.com, Jessica Yu <jeyu@kernel.org>,
	arjan@linux.intel.com, X86 ML <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernel-hardening@lists.openwall.com, rick.p.edgecombe@intel.com
Subject: Re: [PATCH 9/9] module: Reorder functions
Date: Mon, 20 Apr 2020 10:59:50 -0700	[thread overview]
Message-ID: <00b0ea7c94e298e12bc3bfcc1c780dc78056c463.camel@linux.intel.com> (raw)
In-Reply-To: <57fcb4a823003e955b63e81085b7d18a2ac0c139.camel@linux.intel.com>

On Mon, 2020-04-20 at 10:56 -0700, Kristen Carlson Accardi wrote:
> On Mon, 2020-04-20 at 14:01 +0200, Ard Biesheuvel wrote:
> > On Wed, 15 Apr 2020 at 23:07, Kristen Carlson Accardi
> > <kristen@linux.intel.com> wrote:
> > > If a module has functions split out into separate text sections
> > > (i.e. compiled with the -ffunction-sections flag), reorder the
> > > functions to provide some code diversification to modules.
> > > 
> > 
> > Is that the only prerequisite? I.e., is it sufficient for another
> > architecture to add -ffunction-sections to the module CFLAGS to get
> > this functionality? (assuming it defines CONFIG_FG_KASLR=y)
> 
> I think it would work for modules. I've not tested this of course. It
> might not make sense for some architectures (like 32 bit), but it
> would
> probably work.
> 
> > > Signed-off-by: Kristen Carlson Accardi <kristen@linux.intel.com>
> > > Reviewed-by: Kees Cook <keescook@chromium.org>
> > > ---
> > >  kernel/module.c | 82
> > > +++++++++++++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 82 insertions(+)
> > > 
> > > diff --git a/kernel/module.c b/kernel/module.c
> > > index 646f1e2330d2..e432ec5f6df4 100644
> > > --- a/kernel/module.c
> > > +++ b/kernel/module.c
> > > @@ -53,6 +53,8 @@
> > >  #include <linux/bsearch.h>
> > >  #include <linux/dynamic_debug.h>
> > >  #include <linux/audit.h>
> > > +#include <linux/random.h>
> > > +#include <asm/setup.h>
> > >  #include <uapi/linux/module.h>
> > >  #include "module-internal.h"
> > > 
> > > @@ -2370,6 +2372,83 @@ static long get_offset(struct module *mod,
> > > unsigned int *size,
> > >         return ret;
> > >  }
> > > 
> > > +/*
> > > + * shuffle_text_list()
> > > + * Use a Fisher Yates algorithm to shuffle a list of text
> > > sections.
> > > + */
> > > +static void shuffle_text_list(Elf_Shdr **list, int size)
> > > +{
> > > +       int i;
> > > +       unsigned int j;
> > > +       Elf_Shdr *temp;
> > > +
> > > +       for (i = size - 1; i > 0; i--) {
> > > +               /*
> > > +                * pick a random index from 0 to i
> > > +                */
> > > +               get_random_bytes(&j, sizeof(j));
> > > +               j = j % (i + 1);
> > > +
> > > +               temp = list[i];
> > > +               list[i] = list[j];
> > > +               list[j] = temp;
> > > +       }
> > > +}
> > > +
> > > +/*
> > > + * randomize_text()
> > > + * Look through the core section looking for executable code
> > > sections.
> > > + * Store sections in an array and then shuffle the sections
> > > + * to reorder the functions.
> > > + */
> > > +static void randomize_text(struct module *mod, struct load_info
> > > *info)
> > > +{
> > > +       int i;
> > > +       int num_text_sections = 0;
> > > +       Elf_Shdr **text_list;
> > > +       int size = 0;
> > > +       int max_sections = info->hdr->e_shnum;
> > > +       unsigned int sec = find_sec(info, ".text");
> > > +
> > > +       if (sec == 0)
> > > +               return;
> > > +
> > > +       text_list = kmalloc_array(max_sections,
> > > sizeof(*text_list),
> > > GFP_KERNEL);
> > > +       if (text_list == NULL)
> > > +               return;
> > > +
> > > +       for (i = 0; i < max_sections; i++) {
> > > +               Elf_Shdr *shdr = &info->sechdrs[i];
> > > +               const char *sname = info->secstrings + shdr-
> > > > sh_name;
> > > +
> > > +               if (!(shdr->sh_flags & SHF_ALLOC) ||
> > > +                   !(shdr->sh_flags & SHF_EXECINSTR) ||
> > > +                   strstarts(sname, ".init"))
> > > +                       continue;
> > > +
> > > +               text_list[num_text_sections] = shdr;
> > > +               num_text_sections++;
> > > +       }
> > > +
> > > +       shuffle_text_list(text_list, num_text_sections);
> > > +
> > > +       for (i = 0; i < num_text_sections; i++) {
> > > +               Elf_Shdr *shdr = text_list[i];
> > > +
> > > +               /*
> > > +                * get_offset has a section index for it's last
> > > +                * argument, that is only used by
> > > arch_mod_section_prepend(),
> > > +                * which is only defined by parisc. Since this
> > > this
> > > type
> > > +                * of randomization isn't supported on parisc, we
> > > can
> > > +                * safely pass in zero as the last argument, as
> > > it
> > > is
> > > +                * ignored.
> > > +                */
> > > +               shdr->sh_entsize = get_offset(mod, &size, shdr,
> > > 0);
> > > +       }
> > > +
> > > +       kfree(text_list);
> > > +}
> > > +
> > >  /* Lay out the SHF_ALLOC sections in a way not dissimilar to how
> > > ld
> > >     might -- code, read-only data, read-write data, small
> > > data.  Tally
> > >     sizes, and place the offsets into sh_entsize fields: high bit
> > > means it
> > > @@ -2460,6 +2539,9 @@ static void layout_sections(struct module
> > > *mod, struct load_info *info)
> > >                         break;
> > >                 }
> > >         }
> > > +
> > > +       if (IS_ENABLED(CONFIG_FG_KASLR) && kaslr_enabled())
> > 
> > kaslr_enabled() only exists [as a function] on x86
> 
> CONFIG_FG_KASLR is dependant on x86_64. If people really think there
> is
> value in having the module randomization not dependent on the kernel
> randomization it can be changed to a different config option - but I
> am
> not sure that there is a ton of value in the module randomization on
> it's own.

I should have added - thank you for pointing this out, I will fix it in
the next version. I was on a tangent about whether you should even use
this without the main kernel randomization :).



  reply	other threads:[~2020-04-20 17:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 21:04 [PATCH 0/9] Function Granular Kernel Address Space Layout Randomization Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 1/9] objtool: do not assume order of parent/child functions Kristen Carlson Accardi
2020-04-22 22:17   ` Josh Poimboeuf
2020-04-15 21:04 ` [PATCH 2/9] x86: tools/relocs: Support >64K section headers Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 3/9] x86/boot: Allow a "silent" kaslr random byte fetch Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 4/9] x86: Makefile: Add build and config option for CONFIG_FG_KASLR Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 5/9] x86: make sure _etext includes function sections Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 6/9] x86/tools: Adding relative relocs for randomized functions Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 7/9] x86: Add support for function granular KASLR Kristen Carlson Accardi
2020-04-16  0:14   ` kbuild test robot
2020-05-15  5:55   ` Baoquan He
2020-04-15 21:04 ` [PATCH 8/9] kallsyms: hide layout Kristen Carlson Accardi
2020-04-20 11:58   ` Ard Biesheuvel
2020-04-20 17:46     ` Kristen Carlson Accardi
2020-04-15 21:04 ` [PATCH 9/9] module: Reorder functions Kristen Carlson Accardi
2020-04-20 12:01   ` Ard Biesheuvel
2020-04-20 13:37     ` Arjan van de Ven
2020-04-20 13:43       ` Ard Biesheuvel
2020-04-20 13:47         ` Arjan van de Ven
2020-04-20 17:56     ` Kristen Carlson Accardi
2020-04-20 17:59       ` Kristen Carlson Accardi [this message]
2020-04-22 16:22         ` Ard Biesheuvel
2020-04-22 18:02           ` Kristen Carlson Accardi
2020-04-20 17:48 ` [PATCH 0/9] Function Granular Kernel Address Space Layout Randomization Kees Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00b0ea7c94e298e12bc3bfcc1c780dc78056c463.camel@linux.intel.com \
    --to=kristen@linux.intel.com \
    --cc=ardb@kernel.org \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jeyu@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox