News for hackers. Stuff that matters.
Re:QEMU: user-to-root privesc inside VM via bad translation ... by thesz on Wednesday March 22, 2017 @09:18AM (#13930631)
Range checking is done deal with sufficiently strong types (read - dependent types). It was done in the Epigram LONG time ago, ten years ago if not more.

For example, when you fetching bytes for decode you can type-check that you are in the quota and act accordingly.

Re:QEMU: user-to-root privesc inside VM via bad translation ... by tyingq on Wednesday March 22, 2017 @09:48AM (#13930825)
Still a developer choice as to what the quota is though, right? That's the logic error here, quota set too high.
Re:QEMU: user-to-root privesc inside VM via bad translation ... by thesz on Wednesday March 22, 2017 @06:04PM (#13935425)
No.

Working with two page quota (as QEMU dev intended) at type level won't allow you to pass through three page (as QEMU code allows and what is exploited).