← Back to context Comment by UltraSane 3 hours ago By a LOT. It would expose the data Windows keeps isolated using virtualization based security. 3 comments UltraSane Reply odo1242 2 hours ago Does this mean the exploit can be used in a VM to get access to the host machine? smaudet 1 hour ago Not necessarily. A VM doesn't have a "real" DMA controller, and this exploit is specific to a family of real hardware CPUs.Its not to say that its not impressive, but its fairly isolated to a specific family of processors from 2013. odo1242 10 minutes ago Oh, right. I forgot that DMA controllers are virtualized on VMs.
odo1242 2 hours ago Does this mean the exploit can be used in a VM to get access to the host machine? smaudet 1 hour ago Not necessarily. A VM doesn't have a "real" DMA controller, and this exploit is specific to a family of real hardware CPUs.Its not to say that its not impressive, but its fairly isolated to a specific family of processors from 2013. odo1242 10 minutes ago Oh, right. I forgot that DMA controllers are virtualized on VMs.
smaudet 1 hour ago Not necessarily. A VM doesn't have a "real" DMA controller, and this exploit is specific to a family of real hardware CPUs.Its not to say that its not impressive, but its fairly isolated to a specific family of processors from 2013. odo1242 10 minutes ago Oh, right. I forgot that DMA controllers are virtualized on VMs.
Does this mean the exploit can be used in a VM to get access to the host machine?
Not necessarily. A VM doesn't have a "real" DMA controller, and this exploit is specific to a family of real hardware CPUs.
Its not to say that its not impressive, but its fairly isolated to a specific family of processors from 2013.
Oh, right. I forgot that DMA controllers are virtualized on VMs.