linux-kernel - Re: [PATCH] exec: Avoid RLIMIT

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

Message-ID: <20171129182004.GF14545@mail.hallyn.com>
Date:   Wed, 29 Nov 2017 12:20:04 -0600
From:   "Serge E. Hallyn" <serge@...lyn.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        James Morris <james.l.morris@...cle.com>,
        Serge Hallyn <serge@...lyn.com>,
        Andy Lutomirski <luto@...nel.org>,
        Oleg Nesterov <oleg@...hat.com>, Jiri Slaby <jslaby@...e.cz>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] exec: Avoid RLIMIT_STACK races with prlimit()

Quoting Kees Cook (keescook@...omium.org):
> While the defense-in-depth RLIMIT_STACK limit on setuid processes was
> protected against races from other threads calling setrlimit(), I missed
> protecting it against races from external processes calling prlimit().
> This adds locking around the change and makes sure that rlim_max is set
> too.
> 
> Reported-by: Ben Hutchings <ben.hutchings@...ethink.co.uk>
> Reported-by: Brad Spengler <spender@...ecurity.net>
> Fixes: 64701dee4178e ("exec: Use sane stack rlimit under secureexec")
> Cc: stable@...r.kernel.org
> Cc: James Morris <james.l.morris@...cle.com>
> Cc: Serge Hallyn <serge@...lyn.com>

Acked-by: Serge Hallyn <serge@...lyn.com>

The only thing i'm wondering is in do_prlimit():

. 1480         if (new_rlim) {
. 1481                 if (new_rlim->rlim_cur > new_rlim->rlim_max)
. 1482                         return -EINVAL;

that bit is done not under the lock.  Does that still allow a
race, if this check is done before the below block, and then the
rest proceeds after?

I *think* not, because later in do_prlimit() it will return -EPERM if

. 1500                 if (new_rlim->rlim_max > rlim->rlim_max &&
. 1501                                 !capable(CAP_SYS_RESOURCE))

Although rlim is gathered before the lock, but that is a struct *
so should be ok?

> Cc: Andy Lutomirski <luto@...nel.org>
> Cc: Oleg Nesterov <oleg@...hat.com>
> Cc: Jiri Slaby <jslaby@...e.cz>
> Signed-off-by: Kees Cook <keescook@...omium.org>
> ---
>  fs/exec.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/exec.c b/fs/exec.c
> index 1d6243d9f2b6..6be2aa0ab26f 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1340,10 +1340,15 @@ void setup_new_exec(struct linux_binprm * bprm)
>  		 * avoid bad behavior from the prior rlimits. This has to
>  		 * happen before arch_pick_mmap_layout(), which examines
>  		 * RLIMIT_STACK, but after the point of no return to avoid
> -		 * needing to clean up the change on failure.
> +		 * races from other threads changing the limits. This also
> +		 * must be protected from races with prlimit() calls.
>  		 */
> +		task_lock(current->group_leader);
>  		if (current->signal->rlim[RLIMIT_STACK].rlim_cur > _STK_LIM)
>  			current->signal->rlim[RLIMIT_STACK].rlim_cur = _STK_LIM;
> +		if (current->signal->rlim[RLIMIT_STACK].rlim_max > _STK_LIM)
> +			current->signal->rlim[RLIMIT_STACK].rlim_max = _STK_LIM;
> +		task_unlock(current->group_leader);
>  	}
>  
>  	arch_pick_mmap_layout(current->mm);
> -- 
> 2.7.4
> 
> 
> -- 
> Kees Cook
> Pixel Security