CVE-2018-3615:KO in 5.0.0-20-lowlatency?

Asked by eris23 on 2019-07-07

I'm running 5.0.0-20-lowlatency on

cpu family : 6
microcode : 0xb4
model : 142
model name : Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
stepping : 9

With both intel-microcode 3.20190514.1ubuntu1 and 3.20190618.0ubuntu0.19.04.1
spectre-meltdown-checker https://github.com/speed47/spectre-meltdown-checker

shows

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
* CPU microcode mitigates the vulnerability: NO
> STATUS: VULNERABLE (your CPU supports SGX and the microcode is not up to date)

Is this an error with spectre-meltdown-checker or the intel-microcode package?

This seems to be a long running problem.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu intel-microcode Edit question
Assignee:
No assignee Edit question
Last query:
2019-07-07
Last reply:
2019-07-07
Manfred Hampl (m-hampl) said : #1

If I look at https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-3615.html and https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/L1TF I see that this CVE should not be relevant for Ubuntu at all.

When digging into the spectre-meltdown-checker source, I see the the rating for this vulnerability depends on the answer to another check.

If you search your output for
  * L1 data cache invalidation
    * FLUSH_CMD MSR is available:
What exactly is shown there and in the three lines to follow?

eris23 (jdkatz23) said : #2

  * L1 data cache invalidation
    * FLUSH_CMD MSR is available: NO
    * CPU indicates L1D flush capability: YES (L1D flush feature bit)

Manfred Hampl (m-hampl) said : #3

What are the few lines including and below
* CPU supports Software Guard Extensions (SGX):

eris23 (jdkatz23) said : #4

  * CPU supports Software Guard Extensions (SGX): YES
  * CPU microcode is known to cause stability problems: NO (model 0x8e family 0x6 stepping 0x9 ucode 0xb4 cpuid 0x806e9)
  * CPU microcode is the latest known available version: YES (latest version is 0xb4 dated 2019/04/01 according to builtin MCExtractor DB v112 - 2019/05/22)
* CPU vulnerability to the speculative execution attack variants
  * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
  * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
  * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
  * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read): YES
  * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass): YES
  * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): YES
  * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): YES
  * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): YES
  * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): YES
  * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): YES
  * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): YES
  * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): YES

Manfred Hampl (m-hampl) said : #5

This is somewhat contradictory:

CPU microcode is the latest known available version: YES
versus
your CPU supports SGX and the microcode is not up to date

I think you better try discussing this at the spectre-meltdown-checker pages.

eris23 (jdkatz23) said : #6

Can you help with this problem?

Provide an answer of your own, or ask eris23 for more information if necessary.

To post a message you must log in.