Re: patch openSUSE-2019-1806 fails to mitigate CVE-2018-12126/CVE-2018-12130/CVE-2018-12127/CVE-2019-11091 ?

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ua5P4a85WpNkeyFpDQkBj1bwcM4pwaCFz
Content-Type: multipart/mixed; boundary="lq2M8M1cDOQbk26Y6CJGkt83116e0rpBK"

--lq2M8M1cDOQbk26Y6CJGkt83116e0rpBK
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-CA
Content-Transfer-Encoding: quoted-printable

On 13/02/2020 08.30, Marcus Meissner wrote:
 > Hi,
 >
 > On Wed, Feb 12, 2020 at 08:29:53PM -0800, PGNet Dev wrote:
 >> This security update
 >>
 >>=20
https://lists.opensuse.org/opensuse-security-announce/2019-07/msg00052.ht=
ml
 >>
 >>
 >>
addresses

=2E..

 >> on an old, but otherwise functional, laptop,
 >>
 >> cat /proc/cpuinfo | grep -i "model name" model name : Intel(R)
 >> Core(TM) i3 CPU M 370  @ 2.40GHz

=2E..

 >> a check with
 >>
 >> spectre-meltdown-checker.sh --version Spectre and Meltdown
 >> mitigation detection tool v0.43
 >>
 >> returns

=2E..

 >> and
 >>
 >> cat /sys/devices/system/cpu/vulnerabilities/mds Vulnerable: Clear
 >> CPU buffers attempted, no microcode; SMT disabled
 >>
 >> what additional mitigation, &/or specific microcode update is
 >> required to complete the mitigations?
 >
 > A newer processor. :/
 >
 > Sadly, Intel does not provide updated microcode for older
 > processors.

Doesn't the Linux kernel include other mitigations besides Intel
provided microcode?

If only new processors are covered by them, we are doomed. :-(

--=20
Cheers / Saludos,

		Carlos E. R.
		(from 15.1 x86_64 at Telcontar)


--lq2M8M1cDOQbk26Y6CJGkt83116e0rpBK--

--ua5P4a85WpNkeyFpDQkBj1bwcM4pwaCFz
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkUnzAAKCRC1MxgcbY1H
1XsIAJsGZn9xSWbVtqor9FEu2xwtybA5GACfbcrSeI97vghsU3a9RNZJEs2JRIo=
=o70k
-----END PGP SIGNATURE-----

--ua5P4a85WpNkeyFpDQkBj1bwcM4pwaCFz--
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]