Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 19 Jan 2016 11:09:06 -0800
From: Andy Lutomirski <>
To: Kees Cook <>
Cc: Ingo Molnar <>, "H. Peter Anvin" <>, 
	Michael Ellerman <>, Mathias Krause <>, 
	Thomas Gleixner <>, X86 ML <>, Arnd Bergmann <>, 
	PaX Team <>, Emese Revfy <>, 
	"" <>, 
	"" <>, linux-arch <>
Subject: Re: [PATCH v4 8/8] x86, vdso: mark vDSO read-only after init

On Tue, Jan 19, 2016 at 10:08 AM, Kees Cook <> wrote:
> The vDSO does not need to be writable after __init, so mark it as
> __ro_after_init. The result kills the exploit method of writing to the
> vDSO from kernel space resulting in userspace executing the modified code,
> as shown here to bypass SMEP restrictions:
> The memory map (with added vDSO address reporting) shows the vDSO moving
> into read-only memory:

Acked-by: Andy Lutomirski <>

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.