Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upMemory dedup exploitation resilience #2104
Comments
marmarek
added
the
invalid
label
Jun 21, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Jun 21, 2016
Member
We don't use any memory deduplication (which in Xen is only part of experimental, unsupported, disabled by default "tmem").
|
We don't use any memory deduplication (which in Xen is only part of experimental, unsupported, disabled by default "tmem"). |
marmarek
closed this
Jun 21, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rudd-O commentedJun 21, 2016
Qubes OS version (e.g.,
R3.1):Any.
Affected TemplateVMs (e.g.,
fedora-23, if applicable):Not pertinent.
There appears to be a way to reliable exploit a combo of Rowhammer and kernel samepage merging / Xen memory dedup: http://www.cs.vu.nl//~kaveh/pubs/pdf/dedup-sp16.pdf -- by the nature of the attack, this might work in a cross-VM fashion.
IF there exist any facilities that would enable such an exploit on Qubes OS, there should be a setting defaulting to off to toggle those facilities.