> > In the Project Zero Stagefright post > > (http://googleprojectzero.blogspot.com/2015/09/stagefrightened.html) > > , > > we see that the linear allocation of memory combined with the low > > number of bits in the initial mmap offset resulted in a much more > > predictable layout which aided the attacker. The initial random mmap > > base range was increased by Daniel Cashman in > > d07e22597d1d355829b7b18ac19afa912cf758d1, but we've done nothing to > > address page relative attacks. > > > > Inter-mmap randomization will decrease the predictability of later > > mmap() allocations, which should help make data structures harder to > > find in memory. In addition, this patch will also introduce unmapped > > gaps between pages, preventing linear overruns from one mapping to > > another another mapping. I am unable to quantify how much this will > > improve security, but it should be > 0. > > One person calls "unmapped gaps between pages" a feature, others call > it > a mess. ;-) It's very hard to quantify the benefits of fine-grained randomization, but there are other useful guarantees you could provide. It would be quite helpful for the kernel to expose the option to force a PROT_NONE mapping after every allocation. The gaps should actually be enforced. So perhaps 3 things, simply exposed as off-by-default sysctl options (no need for special treatment on 32-bit): a) configurable minimum gap size in pages (for protection against linear and small {under,over}flows) b) configurable minimum gap size based on a ratio to allocation size (for making the heap sparse to mitigate heap sprays, especially when mixed with fine-grained randomization - for example 2x would add a 2M gap after a 1M mapping) c) configurable maximum random gap size (the random gap would be in addition to the enforced minimums) The randomization could just be considered an extra with minor benefits rather than the whole feature. A full fine-grained randomization implementation would need a higher-level form of randomization than gaps in the kernel along with cooperation from userspace allocators. This would make sense as one part of it though.
Attachment:
signature.asc
Description: This is a digitally signed message part