Messages in this thread | | | From | Andy Lutomirski <> | Date | Tue, 19 Jan 2016 11:09:06 -0800 | 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 <keescook@chromium.org> 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: http://itszn.com/blog/?p=21 > > The memory map (with added vDSO address reporting) shows the vDSO moving > into read-only memory:
Acked-by: Andy Lutomirski <luto@kernel.org>
| |