[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160802081438.GE9601@gmail.com>
Date: Tue, 2 Aug 2016 10:14:56 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Thomas Garnier <thgarnie@...gle.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
Kees Cook <keescook@...omium.org>, x86@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH] x86/mm: Enable KASLR for vmemmap memory region (x86_64)
* Thomas Garnier <thgarnie@...gle.com> wrote:
> On Wed, Jul 27, 2016 at 8:59 AM, Thomas Garnier <thgarnie@...gle.com> wrote:
> > Add vmemmap in the list of randomized memory regions.
> >
> > The vmemmap region holds a representation of the physical memory (through
> > a struct page array). An attacker could use this region to disclose the
> > kernel memory layout (walking the page linked list).
> >
> > Signed-off-by: Thomas Garnier <thgarnie@...gle.com>
> > Signed-off-by: Kees Cook <keescook@...omium.org>
> > ---
> > Missing patch didn't pick-up by the tip bot on KASLR memory randomization.
> > Resending after rebase on tip and tests as discussed with Ingo.
> > Based on tip 4bcc8cf6ab5932cbb2511c8e18065e61b069f21c
>
> Ingo: Any comment? Can you integrate it on tip?
>
> > ---
> > arch/x86/include/asm/kaslr.h | 1 +
> > arch/x86/include/asm/pgtable_64_types.h | 4 +++-
> > arch/x86/mm/kaslr.c | 24 +++++++++++++++++++++++-
> > 3 files changed, 27 insertions(+), 2 deletions(-)
After the merge window is over. There's no bad effect from the lack of this patch,
other than lower level of randomization of kernel virtual addresses, right?
Thanks,
Ingo
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
