![Adam [he/him]](https://pbs.twimg.com/profile_images/2328235588/mky7liyb93paqco9cfuk_normal.gif)
It would be cute to use Meltdown to read the MAC keys used to protect the Switch kernel from GPU DMA attacks.
Apple, Nvidia, Qualcomm, Marvell, and Cavium all make custom ARM cores and none of them have any info on whether their cores are affected by Spectre/Meltdown and available mitigations. Don't forget about non-Cortex cores!
-
-
-
It would, but given the speed at which Switch hacking has been moving recently... I think that won't be necessary.
End of conversation
New conversation -
-
-
That is about OS-level mitigations. It says exactly nothing about specific CPU microarchitectures and how they're affected. I bet Apple's cores are affected by the misprediction issue, and you can't patch that one at the OS level.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Apple have stated that their devices are affected
-
But have given zero details as to what CPU microarchitectures and what bugs specifically.
- Show replies
New conversation -
-
-
Some higher end MIPS processors are also likely to be affected but nobody said anything about that either ;) Example: https://www.mips.com/products/warrior/p-class-p6600-multiprocessor-core/ …
-
Yes, I'm not even considering other arches yet.
End of conversation
New conversation -
-
-
At this point in time, let’s just assume that anything using OOO = pwned. Anything not using OOO like Apple watch = not pwned.
-
For the basic misprediction attack, yes, assuming anything OOO is pwned is a pretty safe assumpion. But whether branch target injection and cross-privilege reads work or not is a very important question for OOO cores. Those aren't a given.
- Show replies
New conversation -
-
-
Apple implied that iOS and tvOS were affected by Meltdown(!?), but not watchOS???
-
Their article is so light on detail it's completely meaningless. They need to actually list CPU cores and specific vulns. Some A* CPUs just use Cortex cores.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.