[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 24 Apr 2018 19:29:05 +0400
From: Igor Stoppa <igor.stoppa@...il.com>
To: lazytyped <lazytyped@...il.com>, Matthew Wilcox <willy@...radead.org>
Cc: keescook@...omium.org, paul@...l-moore.com, sds@...ho.nsa.gov,
mhocko@...nel.org, corbet@....net, labbott@...hat.com,
linux-cc=david@...morbit.com, --cc=rppt@...ux.vnet.ibm.com,
--security-module@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com,
Igor Stoppa <igor.stoppa@...wei.com>,
Carlos Chinea Perez <carlos.chinea.perez@...wei.com>,
Remi Denis Courmont <remi.denis.courmont@...wei.com>
Subject: Re: [PATCH 7/9] Pmalloc Rare Write: modify selected pools
On 24/04/18 19:03, lazytyped wrote:
>
>
> On 4/24/18 4:44 PM, Matthew Wilcox wrote:
>> On Tue, Apr 24, 2018 at 02:32:36PM +0200, lazytyped wrote:
>>> On 4/24/18 1:50 PM, Matthew Wilcox wrote:
>>>> struct modifiable_data {
>>>> struct immutable_data *d;
>>>> ...
>>>> };
>>>>
>>>> Then allocate a new pool, change d and destroy the old pool.
>>> With the above, you have just shifted the target of the arbitrary write
>>> from the immutable data itself to the pointer to the immutable data, so
>>> got no security benefit.
>> There's always a pointer to the immutable data. How do you currently
>> get to the selinux context? file->f_security. You can't make 'file'
>> immutable, so file->f_security is the target of the arbitrary write.
>> All you can do is make life harder, and reduce the size of the target.
>
> So why adding an extra pointer/indirection helps here? It adds attacking
> surface.
>>
>>> The goal of the patch is to reduce the window when stuff is writeable,
>>> so that an arbitrary write is likely to hit the time when data is read-only.
>> Yes, reducing the size of the target in time as well as bytes. This patch
>> gives attackers a great roadmap (maybe even gadget) to unprotecting
>> a pool.
>
> I don't think this is relevant to the threat model this patch addresses.
> If the attacker can already execute code, it doesn't matter whether this
> specific piece of code exists or not. In general, if an attacker got to
> the point of using gadgets, you've lost.
Realistically, if the attacker can execute arbitrary code, through
gadgets, there is nothing preventing a direct attack to the physical
page, by remapping it, exactly like the patch does.
Or even changing the page table.
Wrt re-utilizing this specific rare_write() function, it would be
possible to mark it as __always_inline, so that it will be executed only
with the data and pool it is intended for.
Then, if one has access to a compiler plugin that does CFI, it becomes
harder to reuse the inlined function.
Inlining should not be too bad, as size overhead.
OTOH, having the pointer always laying around at a specific address,
allows for easier scanning - and attack - of the data
The remapping to a temporary address should make it harder to figure out
where to write to.
Again, the whole assumption behind pmalloc is that the attacker can do
read and writes, maybe limited execution, in the form of function calls.
But if the attacker can execute arbitrary code, all bets are off and the
system is forfeited.
Really critical data should go into a TEE or similar isolated environment.
> On the contrary, it opens the road to design trusted paths that can
> write to or access data that would generally be read-only or not
> accessible (with, of course, all the complexity, limitations and
> penalties of doing this purely in software on a page sized basis).
I had considered the COW approach, where I would allocate a new page and
swap it atomically, but it is not supported on ARM.
--
igor
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.
