From owner-freebsd-security@FreeBSD.ORG  Thu May  8 08:29:49 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E9CCC521
 for <freebsd-security@freebsd.org>; Thu,  8 May 2014 08:29:49 +0000 (UTC)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 A6E6FE6C
 for <freebsd-security@freebsd.org>; Thu,  8 May 2014 08:29:49 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.82 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1WiJi5-0006Hz-S7; Thu, 08 May 2014 12:29:45 +0400
Date: Thu, 8 May 2014 12:29:45 +0400
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Kevin Day <toasty@dragondata.com>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:08.tcp
Message-ID: <20140508082945.GA22384@zxy.spb.ru>
References: <201404300435.s3U4ZAw1093717@freefall.freebsd.org>
 <6D007FDB-D94D-48BD-B066-30A23F9CB472@dragondata.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6D007FDB-D94D-48BD-B066-30A23F9CB472@dragondata.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 May 2014 08:29:50 -0000

On Wed, Apr 30, 2014 at 01:48:41PM -0500, Kevin Day wrote:

> > Affects:        All supported versions of FreeBSD.
> > Corrected:      2014-04-30 04:04:20 UTC (stable/8, 8.4-STABLE)
> >                 2014-04-30 04:05:47 UTC (releng/8.4, 8.4-RELEASE-p9)
> >                 2014-04-30 04:05:47 UTC (releng/8.3, 8.3-RELEASE-p16)
> >                 2014-04-30 04:04:20 UTC (stable/9, 9.2-STABLE)
> >                 2014-04-30 04:05:47 UTC (releng/9.2, 9.2-RELEASE-p5)
> >                 2014-04-30 04:05:47 UTC (releng/9.1, 9.1-RELEASE-p12)
> >                 2014-04-30 04:03:05 UTC (stable/10, 10.0-STABLE)
> >                 2014-04-30 04:04:42 UTC (releng/10.0, 10.0-RELEASE-p2)
> 
> Does anyone know the lower bound for how far back this bug exists? Is it only present in the above versions, or does it affect earlier versions that aren't listed?
> 
> (trying to come up with a deployment plan for some servers stuck on 8.1 and 7.x due to vendors abandoning device drivers)

I think this is result of fixing kern/155407 in r226113 and r228016.