←back to thread

262 points fortran77 | 1 comments | | HN request time: 0.223s | source
Show context
acdha ◴[] No.42189685[source]
Interesting that they’re mentioned as only being exploited on Intel. Has anyone seen whether that’s because the attacker only targeted that platform or is it actually stopped by something like pointer protection?
replies(3): >>42189761 #>>42189809 #>>42189932 #
justinclift ◴[] No.42189809[source]
Doesn't seem to completely line up that they're rushing out iOS updates (ie for phones, etc) for something they're saying they've only confirmed on Intel cpus.

Unless they're assuming it's exploitable on Apple Silicon as well, or are being extra careful just in case.

replies(7): >>42189876 #>>42189883 #>>42190175 #>>42190448 #>>42190733 #>>42190776 #>>42190850 #
1. SoftTalker ◴[] No.42190850[source]
Sometimes problems manifest differently on different architectures. It's one of the advantages of building for more than just one: it shakes out bugs. Doesn't mean you don't fix the root issue in all builds.

Apple for the most part has one codebase that they build for their different architectures. They've been doing this since the NeXT days when they supported Motorola, Intel, Sparc, and maybe a couple of other architectures.