Don't worry about the Pandora, it is absolutely immune to those vulnerabilities. The Cortex-A8 has an in-order architecture, it does not use any kind of speculative execution. This kind of prediction mechanism only makes sense on an out-of-order architecture - which is why the early Intel Atoms are not affected as well.Unfortunately thus far I've not been able to compile the exploits on my Pandora due to them including some x86 constants at the very least.
Check this Cortex-A comparison on Wikipedia, the Cortex-A9 was the first one to introduce an out-of-order architecture. You can check this on ARM's own product page of the A8 as well. It is the only in-order CPU in that list, maybe they just mixed things up, the Cortex-A8 and its direct offsprings are the only Cortex-A class CPUs with an in-order architecture.If, as you say the A8 is an in-order processor (I was unable to verify this or disprove it when I last checked)
From what little I've picked up thus far, the kernel patches are mainly targetting meltdown flaws, in that they protect the kernel from being read by nasty user processes. There's also spectre flaws that let you e.g. read all RAM including other userspaces, and that ARM advisory seems focussed on those flaws to me.From us ? Probably just make sure we're using the right configurations options for the kernel.
Debian have already updated its toolchains even the cross-compiling ones. I havent updated my pyra yet, but i'm pretty sure what need to be recompiled already have been updated by the debian security team
It's not that it doesn't do speculative execution, the point is that if you are not going to reorder instructions for better performance you're simply doing a lot less speculation. See the link about the Xenon CPU I already posted, it's an in-order CPU like the A8 and the old Atoms that are said to not be vulnerable, but it still suffers from an essential design flaw related to speculative execution.Pandora, with Cortex-A8, is inmune as this processor doesn't have especulative execution.
Three academics from Northeastern University and three researchers from IBM Research have discovered a new variation of the Spectre CPU vulnerability that can be exploited via browser-based code.