public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 3/3] arm64/syscalls: Check address limit on user-mode return
Date: Wed, 21 Jun 2017 09:16:01 +0100	[thread overview]
Message-ID: <20170621081601.g6fsf6i3mxzar5sn@localhost> (raw)
In-Reply-To: <20170615011203.144108-3-thgarnie@google.com>

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 <thgarnie@google.com>
> ---
> 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 <catalin.marinas@arm.com>

  reply	other threads:[~2017-06-21  8:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  1:12 [PATCH v10 1/3] x86/syscalls: Check address limit on user-mode return Thomas Garnier
2017-06-15  1:12 ` [PATCH v10 2/3] arm/syscalls: " Thomas Garnier
2017-06-20 20:18   ` Kees Cook
2017-06-20 20:31     ` Thomas Garnier
2017-06-21  9:08       ` Will Deacon
2017-07-18 14:36   ` Leonard Crestez
2017-07-18 16:04     ` Thomas Garnier
2017-07-18 17:18       ` Leonard Crestez
2017-07-18 19:04         ` Thomas Garnier
2017-07-19 14:58           ` Leonard Crestez
2017-07-19 16:51             ` Thomas Garnier
2017-07-19 17:06             ` Russell King - ARM Linux
2017-07-19 17:20               ` [kernel-hardening] " Thomas Garnier
2017-07-19 18:35                 ` Russell King - ARM Linux
2017-07-19 18:50                   ` Thomas Garnier
2017-06-15  1:12 ` [PATCH v10 3/3] arm64/syscalls: " Thomas Garnier
2017-06-21  8:16   ` Catalin Marinas [this message]
2017-06-21 13:57     ` Thomas Garnier
2017-06-20 20:24 ` [PATCH v10 1/3] x86/syscalls: " Kees Cook
2017-06-28 17:52   ` Kees Cook
2017-07-06 20:38     ` Thomas Garnier
2017-07-06 20:48       ` Thomas Gleixner
2017-07-06 20:52         ` Thomas Garnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170621081601.g6fsf6i3mxzar5sn@localhost \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox