Bug 1760200

Summary: hw: EGETKEY erratum
Product: [Other] Security Response Reporter: Wade Mealing <wmealing>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aarapov, esyr, jarodwilson, jonathan, mikedep333, poros, security-response-team, skozina
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-25 22:12:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1764944, 1764945, 1764947, 1764948, 1764949, 1764950, 1764951, 1764952, 1764953, 1764954, 1764955, 1764956, 1766959, 1767760, 1771658    
Bug Blocks: 1752312    

Description Wade Mealing 2019-10-10 06:38:57 UTC 
The Intel SGX functionality provides hardware instructions used to verify a
memory structure has been cryptographically created by the running hardware.
The EGETKEY asembly instruction provides software running in the secure enclave
with keys used by this functionality.

When hyperthreading is enabled a race condition exists where an local attaker
could access the reset key used for the core and from this information derive
the HT-disabled key and use this to emulate/impersonate a HT-disabled platform.
Comment 4 Wade Mealing 2019-11-12 08:25:31 UTC 
Acknowledgements:

Red Hat thanks Intel for reporting this issue and collaborating on the mitigations.
Comment 5 Prasad Pandit 2019-11-12 10:21:34 UTC 
Statement:

Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/solutions/2019-microcode-nov
Comment 6 Prasad Pandit 2019-11-12 10:21:37 UTC 
External References:

https://access.redhat.com/solutions/2019-microcode-nov
Comment 7 Prasad Pandit 2019-11-12 10:21:40 UTC 
Mitigation:

As of this time there are no known mitigations. Please install relevant updated packages to address this flaw.
Comment 8 Prasad Pandit 2019-11-12 18:16:19 UTC 
Created microcode_ctl tracking bugs for this issue:

Affects: fedora-all [bug 1771658]