From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Garnier Subject: Re: [PATCH v10 3/3] arm64/syscalls: Check address limit on user-mode return Date: Wed, 21 Jun 2017 06:57:44 -0700 Message-ID: References: <20170615011203.144108-1-thgarnie@google.com> <20170615011203.144108-3-thgarnie@google.com> <20170621081601.g6fsf6i3mxzar5sn@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20170621081601.g6fsf6i3mxzar5sn@localhost> Sender: linux-kernel-owner@vger.kernel.org To: Catalin Marinas Cc: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andy Lutomirski , Paolo Bonzini , Rik van Riel , Oleg Nesterov , Josh Poimboeuf , Petr Mladek , Miroslav Benes , Kees Cook , Al Viro , Arnd Bergmann , Dave Hansen , David Howells , Russell King , Andy Lutomirski , Will Drewry , Will Deacon , Mark Rutland , Pratyush Anand List-Id: linux-api@vger.kernel.org On Wed, Jun 21, 2017 at 1:16 AM, Catalin Marinas wrote: > On Wed, Jun 14, 2017 at 06:12:03PM -0700, Thomas Garnier wrote: >> Ensure the address limit is a user-mode segment before returning to >> user-mode. Otherwise a process can corrupt kernel-mode memory and >> elevate privileges [1]. >> >> The set_fs function sets the TIF_SETFS flag to force a slow path on >> return. In the slow path, the address limit is checked to be USER_DS if >> needed. >> >> [1] https://bugs.chromium.org/p/project-zero/issues/detail?id=990 >> >> Signed-off-by: Thomas Garnier >> --- >> v10 redesigns the change to use work flags on set_fs as recommended by >> Linus and agreed by others. >> >> Based on next-20170609 >> --- >> arch/arm64/include/asm/thread_info.h | 4 +++- >> arch/arm64/include/asm/uaccess.h | 3 +++ >> arch/arm64/kernel/signal.c | 5 +++++ >> 3 files changed, 11 insertions(+), 1 deletion(-) > > For arm64: > > Reviewed-by: Catalin Marinas Thanks Catalin -- Thomas