linux-kernel - Re: vm86 segfaults with NX bit

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:	Thu, 20 Nov 2008 08:58:44 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: vm86 segfaults with NX bit

On Thu, 20 Nov 2008 16:39:06 +0100
Takashi Iwai <tiwai@...e.de> wrote:

> Hi,
> 
> X guys reported that VESA driver segfaults in vm86 mode with a kernel
> with CONFIG_X86_PAE, and it turned to be the NX bit.  See Novell
> bugzilla #443440:
> 	https://bugzilla.novell.com/show_bug.cgi?id=443440
> 
> I can confirm that the latest 2.6.28-rc still causes the same problem,
> and it disappears when booted with noexec=off option.
> 
> Also, when NX bit is reset for the first 1MB (or smaller) in
> do_sys_vm86(), it also works as expected.  But I have little clue
> where to restore the bit again.
> 
> Any good suggestions / solutions?
> 

did the code that mapped this memory setup use PROT_EXEC ?


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/