So there is no possible set of instructions that could block the particular behavior in the exploit?
In practice, both of these would probably kill performance, so I don't think either of these are great solutions. Recall we are targeting the kernel where everything needs to be as fast as possible.