3 ms·
Can't wait to see what 2017's f00f bug equivalent is after its released. Maybe I should just run his tunneling programs and not wait for the disclosure.
by dcomp 9y ago
Can't wait to see what 2017's f00f bug equivalent is after its released. Maybe I should just run his tunneling programs and not wait for the disclosure.
- anfractuosity 9y agoHe did seem to indicate that was on an esoteric processor though so maybe it's not on an Intel/AMD chip. I don't know much about CPU internals, but would it actually be possible to 'patch' that through updated microcode? It's such a clever program, will be intrigued to see what else it can find!
- deleted 9y ago[deleted]
- wyldfire 9y agoThe f00f bug is one that was discovered when cmpxchg didn't do what it was supposed to. If this just searches the space looking for packets that shouldn't decode but end up getting executed, then it's unlikely to be anywhere as interesting as f00f. In all likelihood we have already seen 2017's big silicon bug and it was AMD's Ryzen 7 1800X issue.
- twiddlydee 9y agoHe says at the end he found a new f00f bug though