From: lazytyped <lazytyped@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [RFC v2] mm: SLAB freelist randomization
Date: Sat, 9 Apr 2016 07:42:02 -0700 [thread overview]
Message-ID: <570914BA.8020308@gmail.com> (raw)
In-Reply-To: <CAJcbSZGo25eo4-ukF39vNvvpdzpmnQY6RVBcxc41Z-goS5F1LA@mail.gmail.com>
On 4/9/16 7:24 AM, Thomas Garnier wrote:
>
> Yes and no. With slabinfo not being available if not root you are not
> sure when you start a new SLAB. You also can't quantify the risk of
> another allocation happening on a real machine under load.
>
> It decreases the odds on a successful overflow that just requires two
> allocations to follow one another. It doesn't mitigate heap overflows.
>
Both things you mention above are somehow unrelated to the freelist
randomization. But that's fine. This has no performance impact, so there
is no problem in having it (not that I would or would want to have a say
:-) ).
I was just arguing that hinting at that specific exploit as one that
would have had 'decreased' odds of exploitation didn't seem like the
best choice.
- twiz
next prev parent reply other threads:[~2016-04-09 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 18:03 [kernel-hardening] [RFC v2] mm: SLAB freelist randomization Thomas Garnier
2016-04-08 18:03 ` Thomas Garnier
2016-04-08 18:03 ` Thomas Garnier
2016-04-09 14:08 ` [kernel-hardening] " lazytyped
2016-04-09 14:24 ` Thomas Garnier
2016-04-09 14:42 ` lazytyped [this message]
2016-04-09 15:31 ` Thomas Garnier
2016-04-11 19:08 ` 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=570914BA.8020308@gmail.com \
--to=lazytyped@gmail.com \
--cc=kernel-hardening@lists.openwall.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 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.