←back to thread

186 points ahlCVA | 1 comments | | HN request time: 0.406s | source
Show context
IAmLiterallyAB ◴[] No.45308000[source]
What's preventing a compromised kernel on one core from hijacking the other cores? This doesn't seem like much of a security boundary
replies(2): >>45308133 #>>45308489 #
1. viraptor ◴[] No.45308133[source]
Nothing prevents it if you achieve code execution. But where it helps is scenarios like syscall / memory mapping exploits where a user process can only affect resources attached to their current kernel. For example https://dirtycow.ninja/ would have a limited scope.