linux-kernel - Re: [PATCH] wait_for_helper: SIGCHLD from user-space can lead to use-after-free

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]

Date:	Wed, 10 Mar 2010 13:27:10 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	David Howells <dhowells@...hat.com>,
	Neil Horman <nhorman@...driver.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] wait_for_helper: SIGCHLD from user-space can lead to
	use-after-free

> Yes. kthreads run with all signal ignored, this is inherited from
> kthreadd() which does ignore_signal().

Ok.

> I don't think this can work. SIG_DFL for SIGCHLD is OK because it is
> sig_kernel_ignore(). But, say, SIGHUP and other signals still should
> be ignored, otherwise we have the same problems with the unwanted
> signal_pending() this patch tries to avoid.

Yes, I see.

> But even if we could do this,
> 
> > That should make it redundant in ____call_usermodehelper,
> > so it could be removed from there.
> 
> Please note that __call_usermodehelper() forks ____call_usermodehelper() too.

Ok.


Thanks,
Roland
--
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/