From: Jiri Slaby <jslaby@suse.cz>
To: mbrugger@suse.com, stable@vger.kernel.org
Cc: Will Deacon <will.deacon@arm.com>, Yann Droneaud <ydroneaud@opteya.com>
Subject: Re: arm64/mm: Remove hack in mmap randomize layout
Date: Tue, 21 Jul 2015 15:55:19 +0200 [thread overview]
Message-ID: <55AE4F47.5080409@suse.cz> (raw)
In-Reply-To: <5009675.v9gvjRB4Io@ubix>
On 07/13/2015, 05:07 PM, Matthias Brugger wrote:
> Hi all,
>
> Commit d6c763afab14 "arm64/mm: Remove hack in mmap randomize layout" fixes a
> security issue which reduces the entropy for mmap base address by half [1].
> A attempt to guess where the stack is mapped via brute-force needs just half
> the attempts.
>
> I found this patch was added to v3.19-rc1 but should be added as well to:
> v3.18, v3.14, v3.12 and v3.10
Applied to 3.12. Thanks.
--
js
suse labs
next prev parent reply other threads:[~2015-07-21 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 15:07 arm64/mm: Remove hack in mmap randomize layout Matthias Brugger
2015-07-15 9:54 ` Yann Droneaud
2015-07-21 13:55 ` Jiri Slaby [this message]
2015-09-11 22:27 ` Greg KH
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=55AE4F47.5080409@suse.cz \
--to=jslaby@suse.cz \
--cc=mbrugger@suse.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=ydroneaud@opteya.com \
/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;
as well as URLs for NNTP newsgroup(s).