3 ms·
There's no need for an OS call. Just userspace access to the same mapped memory is going to stay in the same physical page for far, far, longer than a few hund
by ajross 12y ago
There's no need for an OS call. Just userspace access to the same mapped memory is going to stay in the same physical page for far, far, longer than a few hundred thousand DRAM cycles. Obviously the hard part to an exploit would be locating those corrupt bits elsewhere in the system. That's going to depend entirely on the hardware layout of the DRAM chip.
- witty_username 12y agoAnd I guess ASLR would make it even harder.
- johnsmith108959 12y agoASLR only affects the virtual address space. The physical memory allocations are all probably unaffected by ASLR.
- userbinator 12y agoNot really; if the blocks of memory you allocate are not the desired distance apart, just try again... or allocate a block big enough to guarantee it, then start the alternate read sequence to trigger corruption. Of course this assumes you can already run your code on the machine e.g. in a VM.