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

Date:   Tue, 23 May 2017 18:35:19 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Kees Cook <keescook@...omium.org>
cc:     LKML <linux-kernel@...r.kernel.org>, x86@...utronix.de,
        Masami Hiramatsu <mhiramat@...nel.org>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>
Subject: Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..

On Tue, 23 May 2017, Kees Cook wrote:
> On Tue, May 23, 2017 at 8:40 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> > As of 4.12-rc1 one of my machines triggers the insecure W+X mapping.
>
> > It's consistenly 9 entries close to the beginning of the module space,
> > before the first actual module starts. See below.
> >
> > Any ideas which avoid bisecting would be appreciated.
> 
> Is this the same as:
> 
> https://lkml.org/lkml/2017/5/19/899
> 
> ?
> 
> The location is very similar.

CONFIG_KPROBES_SANITY_TEST=n does not make it go away, but I suspect it's
something in that area, as I recently switched on all of these self tests.

I'll dig into it later today. Need to walk the dogs first.

Thanks,

	tglx