From: "Huang, Kai" <kai.huang@intel.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"Annapurve, Vishal" <vannapurve@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Cai, Chong" <chongc@google.com>,
"Bondarevska, Nataliia" <bondarn@google.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v14 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves
Date: Thu, 14 Aug 2025 09:36:30 +0000 [thread overview]
Message-ID: <a75801b6bf56362c0ac9fd4ac2f82f3133b55f1a.camel@intel.com> (raw)
In-Reply-To: <20250814073640.1507050-6-elena.reshetova@intel.com>
On Thu, 2025-08-14 at 10:34 +0300, Reshetova, Elena wrote:
> == Background ==
>
> ENCLS[EUPDATESVN] is a new SGX instruction [1] which allows enclave
> attestation to include information about updated microcode SVN without a
> reboot. Before an EUPDATESVN operation can be successful, all SGX memory
> (aka. EPC) must be marked as “unused” in the SGX hardware metadata
> (aka.EPCM). This requirement ensures that no compromised enclave can
> survive the EUPDATESVN procedure and provides an opportunity to generate
> new cryptographic assets.
>
> == Solution ==
>
> Attempt to execute ENCLS[EUPDATESVN] every time the first file descriptor
> is obtained via sgx_(vepc_)open(). In the most common case the microcode
> SVN is already up-to-date, and the operation succeeds without updating SVN.
>
> Note: while in such cases the underlying crypto assets are regenerated, it
> does not affect enclaves' visible keys obtained via EGETKEY instruction.
>
> If it fails with any other error code than SGX_INSUFFICIENT_ENTROPY, this
> is considered unexpected and the *open() returns an error. This should not
> happen in practice.
>
> On contrary, SGX_INSUFFICIENT_ENTROPY might happen due to a pressure on the
> system's DRNG (RDSEED) and therefore the *open() can be safely retried to
> allow normal enclave operation.
>
> [1] Runtime Microcode Updates with Intel Software Guard Extensions,
> https://cdrdv2.intel.com/v1/dl/getContent/648682
>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
>
Reviewed-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2025-08-14 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 7:34 [PATCH v14 0/5] Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-14 7:34 ` [PATCH v14 1/5] x86/sgx: Introduce functions to count the sgx_(vepc_)open() Elena Reshetova
2025-08-14 7:34 ` [PATCH v14 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-08-14 7:34 ` [PATCH v14 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-08-14 7:34 ` [PATCH v14 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-08-14 9:35 ` Huang, Kai
2025-08-14 11:48 ` Reshetova, Elena
2025-08-14 22:31 ` Huang, Kai
2025-08-15 12:05 ` Reshetova, Elena
2025-08-14 7:34 ` [PATCH v14 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-14 9:36 ` Huang, Kai [this message]
2025-08-14 16:50 ` Dave Hansen
2025-08-14 21:40 ` Huang, Kai
2025-08-15 6:59 ` Reshetova, Elena
2025-08-18 5:03 ` Huang, Kai
2025-08-18 5:41 ` Reshetova, Elena
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a75801b6bf56362c0ac9fd4ac2f82f3133b55f1a.camel@intel.com \
--to=kai.huang@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bondarn@google.com \
--cc=chongc@google.com \
--cc=dave.hansen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=erdemaktas@google.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=scott.raynor@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=vincent.r.scarlata@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).