2 ms·
You did read the article, right ? It stated that the real problem is in the OpenGL graphics driver, and that the only thing "wrong" with VirtualBox is not prope
by candiodari 8y ago
You did read the article, right ? It stated that the real problem is in the OpenGL graphics driver, and that the only thing "wrong" with VirtualBox is not properly "firewalling"/sanity checking what is passed into it (and the OpenGL driver itself for not properly checking what is passed into the hardware, which can read all memory).
So there's very little point in switching software, assuming you play games with the virtualized system. QEMU ought to be as vulnerable as VirtualBox/VMWare to this problem.
And sure, they could fix this issue by checking this one pointer. But there's going to be 50 more where this problem came from, and they haven't even mentioned bounds checks.
- fulafel 8y ago> QEMU ought to be as vulnerable as VirtualBox/VMWare to this problem. In the GPU passhthrough scenario, the host OS GPU drivers are not involved, and this exact problem won't occur. But it's another question how well the GPU is isolated from the host system using mechanisms like IOMMU. To shield against attacks like manipulating host memory from code running on the GPU.