From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [GIT PULL] one vdso fix for x86/urgent
Date: Sun, 21 Dec 2014 11:18:27 +0100 [thread overview]
Message-ID: <20141221101827.GA769@gmail.com> (raw)
In-Reply-To: <CALCETrUx2xyCn7tmqVKt8A24L+M-EFKrba5kq4Nr75yYsZ4CSQ@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> Hi Ingo, etc,
>
> Please consider pulling for x86/urgent. This fixes a longstanding,
> albeit relatively minor, issue in the x86 vdso randomization
> algorithm. Note that this isn't super-urgent, as this bug isn't
> directly exploitable, and it's as old as the vdso itself.
>
> Thanks,
> Andy
>
> The following changes since commit e589c9e13aeb0c5539bf1314b3a78442ea8fc0c2:
>
> Merge branch 'x86-apic-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2014-12-19
> 14:02:02 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
> tags/pr-20141220-x86-vdso
>
> for you to fetch changes up to 394f56fe480140877304d342dec46d50dc823d46:
>
> x86_64, vdso: Fix the vdso address randomization algorithm
> (2014-12-20 16:56:57 -0800)
>
> ----------------------------------------------------------------
> One vdso fix for a longstanding ASLR bug that's been in the news lately.
>
> The vdso base address has always been randomized, and I don't think there's
> anything particularly wrong with the range over which it's randomized,
> but the implementation seems to have been buggy since the very beginning.
>
> This fixes the implementation to remove a large bias that caused a small
> fraction of possible vdso load addresess to be vastly more likely than
> the rest of the possible addresses.
>
> ----------------------------------------------------------------
> Andy Lutomirski (1):
> x86_64, vdso: Fix the vdso address randomization algorithm
>
> arch/x86/vdso/vma.c | 45 +++++++++++++++++++++++++++++----------------
> 1 file changed, 29 insertions(+), 16 deletions(-)
Pulled into tip:x86/urgent, thanks a lot Andy!
Ingo
prev parent reply other threads:[~2014-12-21 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 1:11 [GIT PULL] one vdso fix for x86/urgent Andy Lutomirski
2014-12-21 10:18 ` Ingo Molnar [this message]
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=20141221101827.GA769@gmail.com \
--to=mingo@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.