linux-kernel - Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..

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] [day] [month] [year] [list]

Date:   Wed, 24 May 2017 08:20:06 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Steven Rostedt <rostedt@...dmis.org>
cc:     Kees Cook <keescook@...omium.org>,
        LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
        Masami Hiramatsu <mhiramat@...nel.org>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..

On Tue, 23 May 2017, Steven Rostedt wrote:

> On Tue, 23 May 2017 22:48:19 +0200 (CEST)
> Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> 
> > It's not KPROBES, it's the new fangled ftrace trampoline code. I
> > added a few printks. All the leaked W+X mappings are allocated via
> > this callchain:
> 
> The trampoline code isn't new. But it has new users because of the
> introduction to synchronize_rcu_tasks(), and there was a bug I fixed in
> -rc2 that moved it down because the test was run before
> synchronize_rcu_tasks() was functional.
> 
> Is this still a bug in rc2?

Yes. Otherwise we wouldn't talking about.

Thanks,

	tglx