One, this isn't Ubuntu-specific.
Two, this is CPU dependent.
Three, the fix is out there.
If you use an Ubuntu derivative, for example, the code will trickle down to you quickly - if it hasn't already. They like to disclose these sorts of things after the fix has been released. It's known as 'responsible disclosure' and it's what the white-hats do in the security industry.
Basically, a white-hat security researcher finds a bug. They then notify the project(s) related. They then give those projects a set period of time. When that time ends, barring other circumstances, they release the info regarding the bug. The project has that much time to issue a fix. They can sometimes ask for more time, but the white-hat knows that the black-hat operators are not dumb. So, they'll often still release the details so that you (the informed consumer) can make a choice about the actions you take.
Make sense?
Two, this is CPU dependent.
Three, the fix is out there.
USN-6286-1: Intel Microcode vulnerabilities | Ubuntu security notices | Ubuntu
Ubuntu is an open source software operating system that runs from the desktop, to the cloud, to all your internet connected things.
ubuntu.com
If you use an Ubuntu derivative, for example, the code will trickle down to you quickly - if it hasn't already. They like to disclose these sorts of things after the fix has been released. It's known as 'responsible disclosure' and it's what the white-hats do in the security industry.
Basically, a white-hat security researcher finds a bug. They then notify the project(s) related. They then give those projects a set period of time. When that time ends, barring other circumstances, they release the info regarding the bug. The project has that much time to issue a fix. They can sometimes ask for more time, but the white-hat knows that the black-hat operators are not dumb. So, they'll often still release the details so that you (the informed consumer) can make a choice about the actions you take.
Make sense?