[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201207200338.GB24625@arm.com>
Date: Mon, 7 Dec 2020 20:03:38 +0000
From: Szabolcs Nagy <szabolcs.nagy@....com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: libc-alpha@...rceware.org, Mark Rutland <mark.rutland@....com>,
Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
Jeremy Linton <jeremy.linton@....com>,
Mark Brown <broonie@...nel.org>,
kernel-hardening@...ts.openwall.com,
Topi Miettinen <toiwoton@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 0/6] aarch64: avoid mprotect(PROT_BTI|PROT_EXEC) [BZ
#26831]
The 12/03/2020 17:30, Catalin Marinas wrote:
> On Fri, Nov 27, 2020 at 01:19:16PM +0000, Szabolcs Nagy wrote:
> > This is v2 of
> > https://sourceware.org/pipermail/libc-alpha/2020-November/119305.html
> >
> > To enable BTI support, re-mmap executable segments instead of
> > mprotecting them in case mprotect is seccomp filtered.
> >
> > I would like linux to change to map the main exe with PROT_BTI when
> > that is marked as BTI compatible. From the linux side i heard the
> > following concerns about this:
> > - it's an ABI change so requires some ABI bump. (this is fine with
> > me, i think glibc does not care about backward compat as nothing
> > can reasonably rely on the current behaviour, but if we have a
> > new bit in auxv or similar then we can save one mprotect call.)
>
> I'm not concerned about the ABI change but there are workarounds like a
> new auxv bit.
>
> > - in case we discover compatibility issues with user binaries it's
> > better if userspace can easily disable BTI (e.g. removing the
> > mprotect based on some env var, but if kernel adds PROT_BTI and
> > mprotect is filtered then we have no reliable way to remove that
> > from executables. this problem already exists for static linked
> > exes, although admittedly those are less of a compat concern.)
>
> This is our main concern. For static binaries, the linker could detect,
> in theory, potential issues when linking and not set the corresponding
> ELF information.
>
> At runtime, a dynamic linker could detect issues and avoid enabling BTI.
> In both cases, it's a (static or dynamic) linker decision that belongs
> in user-space.
note that the marking is tied to an elf module: if the static
linker can be trusted to produce correct marking then both the
static and dynamic linking cases work, otherwise neither works.
(the dynamic linker cannot detect bti issues, just apply user
supplied policy.)
1) if we consider bti part of the semantics of a marked module
then it should be always on if the system supports it and
ideally the loader of the module should deal with PROT_BTI.
(and if the marking is wrong then the binary is wrong.)
2) if we consider the marking to be a compatibility indicator
and let userspace policy to decide what to do with it then the
static exe and vdso cases should be handled by that policy too.
(this makes sense if we expect that there are reasons to turn
bti off for a process independently of markings. this requires
the static linking startup code to do the policy decision and
self-apply PROT_BTI early.)
the current code does not fit either case well, but i was
planning to do (1). and ideally PROT_BTI would be added
reliably, but a best effort only PROT_BTI works too, however
it limits our ability to report real mprotect failures.
> > - ideally PROT_BTI would be added via a new syscall that does not
> > interfere with PROT_EXEC filtering. (this does not conflict with
> > the current patches: even with a new syscall we need a fallback.)
>
> This can be discussed as a long term solution.
>
> > - solve it in systemd (e.g. turn off the filter, use better filter):
> > i would prefer not to have aarch64 (or BTI) specific policy in
> > user code. and there was no satisfying way to do this portably.
>
> I agree. I think the best for now (as a back-portable glibc fix) is to
> ignore the mprotect(PROT_EXEC|PROT_BTI) error that the dynamic loader
> gets. BTI will be disabled if MDWX is enabled.
ok.
we got back to the original proposal: silently ignore mprotect
failures. i'm still considering the mmap solution for libraries
only: at least then libraries are handled reliably on current
setups, but i will have to think about whether attack targets
are mainly in libraries like libc or in executables.
>
> In the meantime, we should start (continue) looking at a solution that
> works for both systemd and the kernel and be generic enough for other
> architectures. The stateless nature of the current SECCOMP approach is
> not suitable for this W^X policy. Kees had some suggestions here but the
> thread seems to have died:
>
> https://lore.kernel.org/kernel-hardening/202010221256.A4F95FD11@keescook/
it sounded like better W^X enforcement won't happen any time soon.
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.
