Return to

Intel FUBAR ... again - Kernel memory leak in nearly every Intel CPU of the last decade (Spectre hits everyone, Meltdown still Intel exclusive)



Did a quick benchmark with a Wine application (most affected by KPTI) on 4.9.75 and Cinebench under Wine used to be at 100% CPU utilization both at normal and very high process priorities with a non KPTI kernel. Now, at both priorities, some cores are given less work so CPU usage would only be around 85% on very high priority. You lose at most 100 Cinebench points on a 6 core hyperthreaded. Heavy multi-threaded workloads are seeming like the ones hit hard by this.

Needless to say, very bad news for the Wine community except on Ryzen. If anyone is crazy enough to run Photoshop CS6 on Wine, you may slow down on image previews by quite a bit.


Move along, nothing to see here. :poop:


I have come to the conclusion this is not a bug, but a feature… for NSA or whomever else.


Why wouldn’t you? Isn’t that exactly what WINE is for? Seems like a pretty reasonable use case to me.


I know people use it for CS6, but the performance loss is measurable for Wine.


well until Linux alternatives stop being rubbish, people just have to deal with that I guess.


So my windows machine has gone fubar. Intel i5 getting insane usage spikes from windows tasks and extremely noticable skipping and freezes in basic browsing and gaming. Clean reinstall and now it’s even worse.


My 4.9.75 Ubuntu machine just went fubar too. Threads literally lock up on my E5-1660 on kernel 4.9.75. All non KPTI kernels are fine, but the KPTI patches causes programs to cause the kernel to fully freeze. It’s not panicing, cause multimedia streams still work, but it’s literally 100% frozen without panicing. A “hard” soft lock.

Went back to 4.13.16 and all was well again. This is a direct impact of the KPTI patches.

Fedora was on the kernel just before KPTI and didn’t release KPTI just yet I think for this specific reason. Also, make sure to get 384.111 Nvidia drivers for 4.14.11 or you risk not being able to boot.

If Page Table Isolation is causing soft hard locks on everything but Haswell and up, that’s just absolutely absurd.


Regressions on updates (especially critical ones like this one that are deployed very fast) can happen with any OS, open source or not, no mater how good the coding is. That is why the forceful updates is a big issue.

If the PTI kernel on linux breaks your PC it is strait forward to roll back until the update is ironed out. Or choose different kernel temporarily that work. In windows you cannot to that. Even if you use recovery the moment you login the update will download and break things gain. That is literally insane and pretty much can trap you on a bricked machine for quite some time. It is already bad for consumer use, add critical systems to this (that often use older hardware) and things get even worse.

it is a very bad idea not to update everything immediately. It is a equally bad idea not to have the option to rollback from regressions as well.

384.111 and 4.14.12 works on my laptop as well (intel wth optimus) on Mint.


Well, CPUs need microcode updates. There is an effort of creating a repo here:

win-raid also have guides how to update your bios with new microcode (UBU) etc. No doubt a lot of motherboard vendors won’t release updated bios. Just like with the IntelME vuln.

Edit: Github repo:


Fairly deep dive into the exploits again this week on security now.


Havent had any issues on my linux machines but we’ll see. Most are on AMD though just my laptops are intel.


What’s weird is my Core 2 Duo laptop is fine with 4.15-RC7, but my E5-1660 chokes on 4.9.75, cause I can’t use 4.15-RC7 on my X79 system cause it has Nvidia GPUs.





I fixed it! Ran dban on both the drives and got an old version of Windows 10 and everything seems to be fixed now.

Until the next patch.


A start at least.


I just installed a BIOS update on a couple Latitude 5480s at work. The update was released 22 Dec, updated yesterday (9 Jan), and includes a microcode update for CVE-2017-5715 along with some ME firmware updates.


AMD the past few days.

Though I kind of doubt a GPU would be impacted by this… idk.