linux-kernel - Re: [systemd-devel] BTI interaction between seccomp filters in systemd and glibc mprotect calls, causing service failures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 22 Oct 2020 13:12:09 +0300
From:   Topi Miettinen <toiwoton@...il.com>
To:     Catalin Marinas <catalin.marinas@....com>,
        Lennart Poettering <mzxreary@...inter.de>
Cc:     Szabolcs Nagy <szabolcs.nagy@....com>,
        Florian Weimer <fweimer@...hat.com>,
        Mark Rutland <mark.rutland@....com>,
        systemd-devel@...ts.freedesktop.org,
        Kees Cook <keescook@...omium.org>,
        Will Deacon <will.deacon@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>, libc-alpha@...rceware.org,
        Dave Martin <dave.martin@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [systemd-devel] BTI interaction between seccomp filters in
 systemd and glibc mprotect calls, causing service failures

On 22.10.2020 12.31, Catalin Marinas wrote:
> On Thu, Oct 22, 2020 at 10:38:23AM +0200, Lennart Poettering wrote:
>> On Do, 22.10.20 09:29, Szabolcs Nagy (szabolcs.nagy@....com) wrote:
>>>>> The dynamic loader has to process the LOAD segments to get to the ELF
>>>>> note that says to enable BTI.  Maybe we could do a first pass and load
>>>>> only the segments that cover notes.  But that requires lots of changes
>>>>> to generic code in the loader.
>>>>
>>>> What if the loader always enabled BTI for PROT_EXEC pages, but then when
>>>> discovering that this was a mistake, mprotect() the pages without BTI? Then
>>>> both BTI and MDWX would work and the penalty of not getting MDWX would fall
>>>> to non-BTI programs. What's the expected proportion of BTI enabled code vs.
>>>> disabled in the future, is it perhaps expected that a distro would enable
>>>> the flag globally so eventually only a few legacy programs might be
>>>> unprotected?
>>>
>>> i thought mprotect(PROT_EXEC) would get filtered
>>> with or without bti, is that not the case?
>>
>> We can adjust the filter in systemd to match any combination of
>> flags to allow and to deny.
> 
> Yes but Szabolcs' point to Topi was that if we can adjust the filters to
> allow mprotect(PROT_EXEC), why not allow mprotect(PROT_EXEC|PROT_BTI)
> instead? Anyway, I see the MDWX and BTI as complementary policies so
> ideally we shouldn't have to choose between one or the other. If we
> allow mprotect(PROT_EXEC), that would override MDWX and also disable
> BTI.

Allowing mprotect(PROT_EXEC|PROT_BTI) would mean that all you need to 
circumvent MDWX is to add PROT_BTI flag. I'd suggest getting the flags 
right at mmap() time or failing that, reverting the PROT_BTI for legacy 
programs later.

Could the kernel tell the loader of the BTI situation with auxiliary 
vectors? Then it would be easy for the loader to always use the best 
mmap() flags without ever needing to mprotect().

-Topi