I agree in general. But in this case - look at the actual source code:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;qemu&#x2F;qemu&#x2F;blob&#x2F;master&#x2F;qemu-seccomp.c" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;qemu&#x2F;qemu&#x2F;blob&#x2F;master&#x2F;qemu-seccomp.c</a><p>There&#x27;s also no further refinement of seccomp privileges at runtime, so that list of syscalls is statically whitelisted up front and nothing else is done (search &#x27;seccomp&#x27; in the repository). Is there anything I obviously <i>couldn&#x27;t</i> achieve with that list of syscalls?<p>Given the list of what&#x27;s whitelisted for the whole process, I wouldn&#x27;t put much stock in it, for now. qemu would probably need some real upgrades and significant work to make this more fine grained and reduce the attack surface using it (both against the kernel and for rogue programs attacking the host qemu instance itself).