linux-kernel - Re: [PATCH v2] do_exit(): Make sure we run with get_fs() == USER

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu,  2 Dec 2010 09:48:01 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	kosaki.motohiro@...fujitsu.com,
	Nelson Elhage <nelhage@...lice.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] do_exit(): Make sure we run with get_fs() == USER_DS.

> > > diff --git a/kernel/exit.c b/kernel/exit.c
> > > index 21aa7b3..68899b3 100644
> > > --- a/kernel/exit.c
> > > +++ b/kernel/exit.c
> > > @@ -914,6 +914,14 @@ NORET_TYPE void do_exit(long code)
> > >  	if (unlikely(!tsk->pid))
> > >  		panic("Attempted to kill the idle task!");
> > >  
> > > +	/*
> > > +	 * If do_exit is called because this processes oopsed, it's possible
> > > +	 * that get_fs() was left as KERNEL_DS, so reset it to USER_DS before
> > > +	 * continuing. This is relevant at least for clearing clear_child_tid in
> > > +	 * mm_release.
> > > +	 */
> > > +	set_fs(USER_DS);
> > 
> > "This is relevant" is no good explanation ;)
> > Please recognize this is tricky code and Please consider to write more 
> > careful and looooong comments.
> 
> I've seen worse comments.  And occasionally none at all :)
> 
> Is this better?
> 
> --- a/kernel/exit.c~do_exit-make-sure-we-run-with-get_fs-==-user_ds-fix
> +++ a/kernel/exit.c
> @@ -917,8 +917,9 @@ NORET_TYPE void do_exit(long code)
>  	/*
>  	 * If do_exit is called because this processes oopsed, it's possible
>  	 * that get_fs() was left as KERNEL_DS, so reset it to USER_DS before
> -	 * continuing. This is relevant at least for clearing clear_child_tid in
> -	 * mm_release.
> +	 * continuing. Amongst other possible reasons, this is to prevent
> +	 * mm_release()->clear_child_tid() from writing to a user-controlled
> +	 * kernel address.
>  	 */

Great!



--
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/