Well it was kill anyway, but now it is definitely kill.
>It hasn't even been 6 months. It's pretty new.
And for a month it was posted about at least a few times a week, and still averages a thread or two a month
It's old news, the only thing that is new here is you, friend
Processor has thing installed on it to make it compatible with programs from 20 years ago. Still on processor 20 years later. Programmer finds exploit to install software that is undetectable by the OS or even kernel.
>undetectable by the OS or even kernel.
CPUs traditionally have a "normal" user mode for programs that limits them from fucking each other up and a kernel mode where trusted OS logic goes that can interfere with normal programs.
When system virtualization was created, a priority mode under (more privileged than) kernel mode was created, and a layer even beneath that was created for Trusted Platform garbage.
The ancient interrupt controller (used to preempt programs whenever a device needed the kernel to do stuff) logic needed to have the hardware memory address it "lived" at movable to prevent some customers' software from breaking, and it turns out there is a sneaky way for pre-Sandy Bridge CPUs to have a normal rootkit move this around and sneak a rootkit into the bottom-most privilege layer that kernels and the hypervisor can't even look at.
>intel in charge of security
This is why I will always chose AMD over intel.
So you're going to eat shit if you have a pre sandy bridge processor and get an uber 1337 rootkit right?
Also what is the attack vectors for this vulnerability? Is it just by USB or could you attack your victim through the net?
Finally, this has already been patched on many new processors and AMD doesn't seem to have this problem so angry birds processors won't be replacing x86 anytime soon.