From owner-svn-src-head@freebsd.org Fri Mar 9 14:27:03 2018 Return-Path: Delivered-To: svn-src-head@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 E9C88F2C87B; Fri, 9 Mar 2018 14:27:02 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 7915D79108; Fri, 9 Mar 2018 14:27:02 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x241.google.com with SMTP id v6so3714591iog.7; Fri, 09 Mar 2018 06:27:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xRN/2P36X4H8wKGPX58koS+k6eRNsAteVTboKweL49c=; b=HVo6phendWmD32eLQ1CFXZQ8+vbpt78PONFHglsfoYCmmFVdQdBbmnnKSsHgCL/41e fz61/mFcT3SmBYUdcFTD37Q3bbXpLOVOcVnzwFM/MTflM3XNM6YvGx4FSMdU9qtPskot ThL8RE1/4Opv7OCe5J92mio0rBcl4efHuc/O56KRZk8ATIGUO2zNMyUkKlO+9MonaUA/ PU17dQP3ka6ZyLlGVscVbKmo7dF8pJLG/le95kUSQv1f/VPdhqyxBXxqKaOVRZ9NVAqK Th207bRnqfJLmWp/AOJAxDh/WzyMOMVte7Tqk+9GxeoqRQ4WIfx6XNj+eFmZlBJ/WM9y fLmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xRN/2P36X4H8wKGPX58koS+k6eRNsAteVTboKweL49c=; b=lTMoTotUg7z23kHKviHl55J1qDgTr79gPmvhQbDNdprT53UITsJ4TGXUlg3O/FlVkF u1lsQT1fJ7lCilhZEzDFCLTHMkS1QuFbljFMw4zLQKzUcqU5aF4f2UUCYcwPaSnbiXW7 ZpmEgrwva0MdJ7gl7sCpXGIbXt+9uPlzhCRIpyY0xehGQrwp7jGdp/K90GSXjq8Mot+H eAd3k9s7lSdbGlvjcfDolJcturG80amxVZnbHvbt5+MZLpn7KlTr/FGrmRl3F9y4U2xV vvtqN9hsSiy01CC72nbpVbggwTvAGNaIMDikrdIffRhum1TlzjrJUC1rTS5zJ8dCUvpp biJw== X-Gm-Message-State: AElRT7GvMVHiJ29SZTIiMVDIBfQw0evUyovrkiWYtl+UmqYqk30ygN+8 vJuA2JibeYpElma/JLNXezRLwndi/L0CEalszt6Jlg== X-Google-Smtp-Source: AG47ELuR5+lBpceVO3kwYcO4VWiDpxSapnf1SLBfAxRupyPrcXtWnac3buNzqLL9pXjLHWWw4eqlAImtehsL7x05yHw= X-Received: by 10.107.134.95 with SMTP id i92mr35399438iod.210.1520605621683; Fri, 09 Mar 2018 06:27:01 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.163.13 with HTTP; Fri, 9 Mar 2018 06:26:40 -0800 (PST) In-Reply-To: References: <201801151837.w0FIb3R7098459@repo.freebsd.org> From: Ed Maste Date: Fri, 9 Mar 2018 09:26:40 -0500 X-Google-Sender-Auth: BzPNyiL6d6ZmFUfxcmOi0dPGV2Q Message-ID: Subject: Re: svn commit: r328011 - in head/sys/amd64/vmm: amd intel To: Kubilay Kocak Cc: FreeBSD Security Team , Tycho Nightingale , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers Content-Type: text/plain; charset="UTF-8" X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 14:27:03 -0000 On 8 March 2018 at 21:57, Kubilay Kocak wrote: > 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? Embargoed patches to address specific security vulnerabilities are handled by secteam, and are committed to all branches simultaneously. For cases like this, where it's a mitigation or other improvement that is already committed to CURRENT, it's best if the domain expert / original committer handles the merge. That said, I'm happy to take care of the merge if desired.