linux-kernel - Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000

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: <fa6086e6-5f89-ec11-d14c-78f8f761b8b7@molgen.mpg.de>
Date:   Thu, 4 Oct 2018 13:00:42 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Jörg Rödel <joro@...tes.org>,
        Thomas Gleixner <tglx@...utronix.de>, linux-mm@...ck.org,
        x86@...nel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000

Dear Borislav,


On 10/04/18 12:54, Borislav Petkov wrote:
> On Thu, Oct 04, 2018 at 10:59:18AM +0200, Paul Menzel wrote:
>> I meant just the test you did.
> 
> https://lkml.kernel.org/r/20181003212255.GB28361@zn.tnic

I see. But there you write, the machine does boot.

While here you write, it did not.

> and I did try marking the ISA range RO in mark_rodata_ro() but the
> machine wouldn't boot after.

>> The SSD is also used in the Lenovo X60 and T60, which are
>> 32-bit systems.
> 
> And what exactly is the problem when you access it on a 64-bit OS?

Sorry I do not understand the question. I carry the SSD drive with
me, and connect it to the ASRock E350M1 (64-bit) or to the Lenovo
X60 laptop and boot from it from both systems.


Kind regards,

Paul


Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)