UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36
Platform: 9592.29.0 (Official Build) dev-channel caroline

Steps to reproduce the problem:
There is a reported Intel flaw with the hyperthread feature that may lead to corruption in certain situations and apparently affects some Chromebooks chips including the Samsung Chromebook Pro:

"TL;DR: unfixed Skylake and Kaby Lake processors could, in some
situations, dangerously misbehave when hyper-threading is enabled.  Disable hyper-threading immediately in BIOS/UEFI to work around the problem.  Read this advisory for instructions about an Intel-provided fix."

Full report:  https://lists.debian.org/debian-devel/2017/06/msg00308.html
Hacker News:  https://news.ycombinator.com/item?id=14630183

A perl script was offered to verify an affected device:

https://lists.debian.org/debian-devel/2017/06/msg00309.html

This was ported to bash and run on the Chromecast Pro in dev mode:

https://forum.xda-developers.com/hardware-hacking/chromebooks/samsung-chromebook-pro-asus-c302ca-t3627253

Or you can verify the same at /proc/cpuinfo.

In any event, the Intel microcode is currently listed as 0x8a and according to the debian post, 0xb9 from Intel contains the fix.

I don't know if this is a chromiumos bug, a bug for Samsung or what, but wanted to bring it to your attention.  Hopefully it can be forwarded or escalated or solved.

What is the expected behavior?
The script should report the Intel microcode patch is up to date and the bug is fixed.

What went wrong?
The bash script reports the following:

cpu 0: 
It's an Intel. Checking model & stepping...
Your CPU is affected by the issue. You should install the latest intel-microcode.
Yours is version 0x8a (138), but you should have at least 0xb9 (185).

Did this work before? N/A 

Chrome version: 60.0.3112.41  Channel: dev
OS Version: 60.0.3112.41
Flash Version: 26.0.0.126

Please update the microcode on the Samsung Chromebook Pro as apparently this bug can lead to data corruption, crashes, etc.

Also, any other devices that use the M3-6Y30 and other skylake/kaby lake processors may be affected and should be fixed if possible.

Thanks!