From owner-svn-src-all@freebsd.org Fri Mar 9 02:58:25 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0F80F4A52C; Fri, 9 Mar 2018 02:58:25 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AB237E936; Fri, 9 Mar 2018 02:58:25 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf0-x242.google.com with SMTP id j2so756952pff.10; Thu, 08 Mar 2018 18:58:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EkVLu1f+wq7uD0we0KaCwg7KI1AFmDG/gzZaqJL6fpw=; b=U0Jo8xidQe8w5aaCnOoBUKKwMJ1J4g0sFyRvzCxNQYkp86w/Jmof2T0pReFqxyoIeA UlAiNPkCVI378dUEX8dSlIQCUs2gG4XohMnNxZOKVO/n5FUiUpudHT5dfGVBdiAhTMif IrlfDJzI5MxY694uHtF4FO0XZzFTMzShhI1qQNysYXa9MEU4/twNtg+YXDNcC+SX26ZL 9+eTyWNpLfELb6Ikrowi9AemYkWPSqKUri0igL/s0BFFrGYYjWtnVm7QhmA1GKt4r79g A1PN+5GT4esxfuub/i2j84HiaqkuCwjJCQL8oa1msvCNu02nkBIL8T2uPYyIE5eNaiJb NQXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=EkVLu1f+wq7uD0we0KaCwg7KI1AFmDG/gzZaqJL6fpw=; b=iABbcLdxb3dxuA7oeAaB6ei5eUBpP9ttqACMEIMvAnCj6TRzTAsTAZ25Fe58KhIdl2 0VemqZCGD2tBR/axYt22IQbbtazHymG52b+TPEVV5fXoypPnB+nSVw6NqvQtZb+ZQTkX eUJuUAd5OKoWm7mLjLfzH3BOoVUmYgSC6HaEULMvvUUKCtdIlTFxPkOB355Taz9xLhIo ExhUnPjFs9E7NlTNK/gkj9mG9pSgCg3DnP+OzCBFQZDH6jFsBYDHn/eKQdHYgaEZTf28 y8LFTmUae1TYNh8ZC7B+yd95zpb7QMWI2TOaWG716VWIduMji0DDuqo661SwGYBkAZsW l4+w== X-Gm-Message-State: APf1xPAP1BflAaCmnUS9wswdU2KzR9c4qai6joK7/1nfTeJM7FxUdyE7 dXtwv/Ot26okywFRuRlLi7uucPoi X-Google-Smtp-Source: AG47ELsCC3wQJnK+nE/0oBtEdIFeHPB42nuwjsdW8rowlHMmRGMBgrQokBbccPMd5XDcoF6f/lkzXQ== X-Received: by 10.99.99.2 with SMTP id x2mr23099986pgb.406.1520564304135; Thu, 08 Mar 2018 18:58:24 -0800 (PST) Received: from [192.168.1.105] (152.94.214.218.sta.wbroadband.net.au. [218.214.94.152]) by smtp.gmail.com with ESMTPSA id n26sm116887pfk.94.2018.03.08.18.58.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Mar 2018 18:58:23 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: svn commit: r328011 - in head/sys/amd64/vmm: amd intel To: Ed Maste , FreeBSD Security Team Cc: Tycho Nightingale , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers References: <201801151837.w0FIb3R7098459@repo.freebsd.org> From: Kubilay Kocak Message-ID: Date: Fri, 9 Mar 2018 13:57:46 +1100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:59.0) Gecko/20100101 Thunderbird/59.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 02:58:26 -0000 On 9/03/2018 8:57 am, Ed Maste wrote: > On 15 January 2018 at 13:37, Tycho Nightingale wrote: >> Author: tychon >> Date: Mon Jan 15 18:37:03 2018 >> New Revision: 328011 >> URL: https://svnweb.freebsd.org/changeset/base/328011 >> >> Log: >> Provide some mitigation against CVE-2017-5715 by clearing registers >> upon returning from the guest which aren't immediately clobbered by >> the host. This eradicates any remaining guest contents limiting their >> usefulness in an exploit gadget. > > Will you MFC this to stable/11? Mitigations and related MFC's and SA's, etc for vulnerabilities, are presumably all being coordinated and handled by secteam, with associated (explicit) messaging when fixes don't apply to particular branches/versions, no?