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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 26 Oct 2014 17:18:19 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Andy Lutomirski <luto@...capital.net> Cc: Richard Weinberger <richard.weinberger@...il.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Kees Cook <keescook@...omium.org>, linux-arch <linux-arch@...r.kernel.org>, Ingo Molnar <mingo@...nel.org>, hpa@...or.com Subject: Re: [PATCH] all arches, signal: Move restart_block to struct task_struct On Sun, Oct 26, 2014 at 10:02:16AM -0700, Andy Lutomirski wrote: > If an attacker can cause a controlled kernel stack overflow, > overwriting the restart block is a very juicy exploit target. > Moving the restart block to struct task_struct prevents this type of > exploit. The hell it does. In a _lot_ of cases current is current_thread_info()->task, which makes your variant just as vulnerable, in addition to being (slightly) more costly. -- 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/
Powered by blists - more mailing lists