From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751658AbcBKRco (ORCPT ); Thu, 11 Feb 2016 12:32:44 -0500 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:9549 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751079AbcBKRcn (ORCPT ); Thu, 11 Feb 2016 12:32:43 -0500 Date: Thu, 11 Feb 2016 18:32:33 +0100 From: Willy Tarreau To: Jiri Slaby Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, "David S . Miller" , Hannes Frederic Sowa Subject: Re: [PATCH 3.12 32/64] unix: properly account for FDs passed over unix sockets Message-ID: <20160211173233.GA27734@1wt.eu> References: <9065c7d8c8be841107dcd6711ab3779553c68fd7.1455198893.git.jslaby@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9065c7d8c8be841107dcd6711ab3779553c68fd7.1455198893.git.jslaby@suse.cz> User-Agent: Mutt/1.4.2.3i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jiri, On Thu, Feb 11, 2016 at 02:59:08PM +0100, Jiri Slaby wrote: > From: willy tarreau > > 3.12-stable review patch. If anyone has any objections, please let me know. > > =============== > > [ Upstream commit 712f4aad406bb1ed67f3f98d04c044191f0ff593 ] > > It is possible for a process to allocate and accumulate far more FDs than > the process' limit by sending them over a unix socket then closing them > to keep the process' fd count low. > > This change addresses this problem by keeping track of the number of FDs > in flight per user and preventing non-privileged processes from having > more FDs in flight than their configured FD limit. > > Reported-by: socketpair@gmail.com > Reported-by: Tetsuo Handa > Mitigates: CVE-2013-4312 (Linux 2.0+) > Suggested-by: Linus Torvalds > Acked-by: Hannes Frederic Sowa > Signed-off-by: Willy Tarreau > Signed-off-by: David S. Miller > Signed-off-by: Jiri Slaby A possible issue was reported regarding this patch, and Hannes implemented a fix that's not yet in mainline. I guess it's preferable to postpone this patch for now. Thanks, Willy