- Intel issued a press release saying they planned to announce this next week after more vendors had patched their shit, which lends me more cause to believe that the Xen bug might be the same one [1]
- Intel claims in the same PR that "many types of computing devices — with many different vendors’ processors" are affected, so I'll be curious to see whether non-Intel platforms fall into the umbrella soon
- macOS implemented partial mitigations in 10.13.2 and apparently has some novel ones coming up in 10.13.3 [2]
- someone reasonably respected claims to have a private PoC of this bug leaking kernel memory [3]
- ARM64 has KPTI patches that aren't in Linus's tree yet [4] [6] ([6] is just a link showing the patches from 4 aren't in Linus's tree as of this writing)
- all the other free operating systems appear to have been left out of the embargoed party (until recently, in FBSD's case), so who knows when they'll have mitigations ready [5]
- So far, Microsoft appears to have only patched Windows 10, so it's unknown whether they intend to backport fixes to 7 or possibly attempt to use this as another crowbar to get people off of XP 2.0
- Update: Microsoft is pushing an OOB update later today that will auto-apply to Win10 but not be forced to auto-apply on 7 and 8 until Tuesday, so that's nice [7]
[1] - https://newsroom.intel.com/news/intel-responds-to-security-r...
[2] - https://twitter.com/aionescu/status/948609809540046849
[3] - https://twitter.com/brainsmoke/status/948561799875502080
[4] - https://patchwork.kernel.org/patch/10095827/
[5] - https://lists.freebsd.org/pipermail/freebsd-security/2018-Ja...
[6] - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
[7] - https://www.theverge.com/2018/1/3/16846784/microsoft-process...