From owner-freebsd-security@FreeBSD.ORG  Fri Nov 23 00:30:16 2012
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id BCABFD73
 for <freebsd-security@freebsd.org>; Fri, 23 Nov 2012 00:30:16 +0000 (UTC)
 (envelope-from bryan-lists@shatow.net)
Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92])
 by mx1.freebsd.org (Postfix) with ESMTP id 62D238FC20
 for <freebsd-security@freebsd.org>; Fri, 23 Nov 2012 00:30:16 +0000 (UTC)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id
 :date:from:mime-version:to:subject:references:in-reply-to
 :content-type:content-transfer-encoding; q=dns; s=sweb; b=PNL9xi
 3x0D4wrPYVhELaEvOUThHu0xlPGQKXT4k/RHhbC8zxPlvGjRC+hdyaEKAp87J8JZ
 TcR+ZlG0xpQk950oAufkWWw+MeAoe0bF2xj9hEFDKc+vPb8XpL96HFen1ptf0y+u
 vi+SwGvRrVTL2NsjwwDpOs1EfVE0bY6VGLlfw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id
 :date:from:mime-version:to:subject:references:in-reply-to
 :content-type:content-transfer-encoding; s=sweb; bh=COKy1/GLzfND
 f3A+zoA0POa16wIRnUI4Tn7GsVQPyk8=; b=cOVc4ocxJDZNQmo0CZRnf0G4+Geq
 YO32N6Xb7bWzIDiv9bKH0KiT0hwWzI3UX51AHBBy68KZl9DyZqCQVEuJ14TTmJOI
 yIPVfXtw4DAYkdTh2F7UuMjAm9ltMqqlDdeMWWKUzY/3VDGq/GNYdNVT1c8Rvhpn
 cV4ZnO6oqI6Huos=
Received: (qmail 89021 invoked from network); 22 Nov 2012 18:30:14 -0600
Received: from unknown (HELO ?10.10.0.115?) (bryan@shatow.net@10.10.0.115)
 by sweb.xzibition.com with ESMTPA; 22 Nov 2012 18:30:14 -0600
Message-ID: <50AEC391.9020105@shatow.net>
Date: Thu, 22 Nov 2012 18:30:09 -0600
From: Bryan Drewery <bryan-lists@shatow.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-12:08.linux
References: <201211230002.qAN023hw018318@freefall.freebsd.org>
In-Reply-To: <201211230002.qAN023hw018318@freefall.freebsd.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 23 Nov 2012 00:30:16 -0000

On 11/22/2012 6:02 PM, FreeBSD Security Advisories wrote:
> IV.  Workaround
> 
> No workaround is available, but systems not using the Linux binary
> compatibility layer are not vulnerable.
> 
> The following command can be used to test if the Linux binary
> compatibility layer is loaded:
> 
> 	# kldstat -m linuxelf

Is it sufficient to kldunload linux?

Bryan