From owner-freebsd-current@freebsd.org Wed Jun 28 14:27:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10F9BDA3452 for ; Wed, 28 Jun 2017 14:27:16 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from borg.macktronics.com (gw.macktronics.com [209.181.253.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E65C67B0F2 for ; Wed, 28 Jun 2017 14:27:13 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from carob.macktronics.com (olive.macktronics.com [209.181.253.66]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by borg.macktronics.com (Postfix) with ESMTPS id 03D0A452 for ; Wed, 28 Jun 2017 09:17:46 -0500 (CDT) Date: Wed, 28 Jun 2017 09:17:45 -0500 (CDT) From: Dan Mack X-X-Sender: mack@localhost.local To: freebsd-current@freebsd.org Subject: fixes for stack clash vulnerability Message-ID: User-Agent: Alpine 2.11 (GSO 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jun 2017 14:27:16 -0000 FreeBSD is mentioned as being vulnerable to this and Qualsys has working exploits which might be released soon: https://blog.qualys.com/securitylabs/2017/06/19/the-stack-clash I don't remember seeing an advisory or seeing any fixes on the svn commit stream so just curious. Dan