linux-kernel - Re: [RFC PATCH v2] x86/arch_prctl: Add ARCH_SET

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:   Wed, 15 Apr 2020 21:16:56 -0400
From:   Keno Fischer <keno@...iacomputing.com>
To:     Andy Lutomirski <luto@...nel.org>
Cc:     Dave Hansen <dave.hansen@...el.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
        "H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andi Kleen <andi@...stfloor.org>,
        Kyle Huey <khuey@...ehuey.com>,
        "Robert O'Callahan" <robert@...llahan.org>
Subject: Re: [RFC PATCH v2] x86/arch_prctl: Add ARCH_SET_XCR0 to set XCR0 per-thread

On Wed, Apr 15, 2020 at 9:14 PM Keno Fischer <keno@...iacomputing.com> wrote:
>
> > Would it make matters easier if tasks with nonstandard XCR0 were not
> > allowed to use ptrace() at all?  And if ARCH_SET_XCR0 were disallowed
> > if the caller is tracing anyone?
>
> That would be fine by me (as long as you're still allowed to ptrace them of
> course).

Sorry, I realized after I had hit send that this wording may not be clear.
What I meant was that it would need to be able to have an external ptracer
(with unmodified XCR0) attach to the task, even if it had modified its XCR0.
I don't think you were suggesting that that wouldn't be possible,
but I just wanted to make sure.