linux-kernel - Apollo Lake with newer microcode: not affected by meltdown anymore?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.21.1808281225550.27853@er-systems.de>
Date:   Tue, 28 Aug 2018 12:27:04 +0200 (CEST)
From:   Thomas Voegtle <tv@...96.de>
To:     x86@...nel.org, linux-kernel@...r.kernel.org, tglx@...utronix.de,
        mingo@...hat.com
Subject: Apollo Lake with newer microcode: not affected by meltdown anymore?


Hello,

Kernel 4.18.5 with old microcode:

[    0.000000] microcode: microcode updated early to revision 0x2c, date =
2017-03-25
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Mitigation: PTI


Kernel 4.18.5 with new microcode (microcode-20180807.tgz), same config:

[    0.000000] microcode: microcode updated early to revision 0x32, date =
2018-05-11
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Not affected


This happens with 4.14.y and 4.9.y as well.

The same with ssb:
old microcode: spec_store_bypass:Vulnerable
new microcode: spec_store_bypass:Not affected

Is this intentional behavior? I have never seen this on other CPUs, such
as Gemini Lake or Baytrail, Haswell etc.

This is a Lenovo Ideapad 120S-11IAP with Apollo Lake N3350 (Goldmont)


    Thomas