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]
Message-ID: <361242c4-261c-1ddb-b948-c71f672779a8@linux.intel.com>
Date:   Wed, 18 Apr 2018 13:33:55 -0700
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Fengguang Wu <fengguang.wu@...el.com>
Cc:     Linux Memory Management List <linux-mm@...ck.org>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Kees Cook <keescook@...omium.org>,
        Serge Hallyn <serge@...lyn.com>,
        James Morris <james.l.morris@...cle.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        lkp@...org
Subject: Re: [do_execve] attempted to set unsupported pgprot

On 04/18/2018 12:59 PM, Andrew Morton wrote:
>> [   12.348499] ------------[ cut here ]------------
>> [   12.349193] attempted to set unsupported pgprot: 8000000000000025 bits: 8000000000000000 supported: 7fffffffffffffff
>> [   12.350792] WARNING: CPU: 0 PID: 1 at arch/x86/include/asm/pgtable.h:540 handle_mm_fault+0xfc1/0xfe0:
>> 						check_pgprot at arch/x86/include/asm/pgtable.h:535
>> 						 (inlined by) pfn_pte at arch/x86/include/asm/pgtable.h:549
>> 						 (inlined by) do_anonymous_page at mm/memory.c:3169
>> 						 (inlined by) handle_pte_fault at mm/memory.c:3961
>> 						 (inlined by) __handle_mm_fault at mm/memory.c:4087
>> 						 (inlined by) handle_mm_fault at mm/memory.c:4124
>> [   12.352294] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.17.0-rc1 #172
>> [   12.353357] EIP: handle_mm_fault+0xfc1/0xfe0:
>> 						check_pgprot at arch/x86/include/asm/pgtable.h:535
>> 						 (inlined by) pfn_pte at arch/x86/include/asm/pgtable.h:549
>> 						 (inlined by) do_anonymous_page at mm/memory.c:3169
>> 						 (inlined by) handle_pte_fault at mm/memory.c:3961
>> 						 (inlined by) __handle_mm_fault at mm/memory.c:4087
>> 						 (inlined by) handle_mm_fault at mm/memory.c:4124
> Dave, fb43d6cb91ef57 ("x86/mm: Do not auto-massage page protections")
> looks like a culprit?


This looks like NX somehow getting set on a system where it is
unsupported.  Any idea what kind of VMA it is?  We probably should have
kept NX from getting set in vm_page_prot to begin with.
>         entry = mk_pte(page, vma->vm_page_prot);
>         if (vma->vm_flags & VM_WRITE)
>                 entry = pte_mkwrite(pte_mkdirty(entry));
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ