linux-kernel - Re: [PATCH] Hardening memory maunipulation.

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] [day] [month] [year] [list]

Message-ID: <554156A1.3010903@kernel.org>
Date:	Wed, 29 Apr 2015 15:09:37 -0700
From:	Andy Lutomirski <luto@...nel.org>
To:	Shawn Chang <citypw@...il.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
CC:	spender@...ecurity.net, keescook@...omium.org
Subject: Re: [PATCH] Hardening memory maunipulation.

On 04/29/2015 08:39 AM, Shawn Chang wrote:
> From: Shawn C <citypw@...il.com>
>
> Hi kernel maintainers,
>
> It won't allow the address above the TASK_SIZE being mmap'ed( or mprotect'ed).
> This patch is from PaX/Grsecurity.
>
> Thanks for your review time!

Does this actually reduce the attack surface of anything?

These functions all search for vmas.  If there's a vma outside of the 
user range, we have a problem.

Also, that use of TASK_SIZE is IMO ridiculous.  Shouldn't be TASK_SIZE_MAX?

--Andy, who is annoyed every time another pointless TIF_IA32 reference, 
even hidden in a macro, makes it into the kernel
--
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/