4 ms·
I wonder if having a separate stick of RAM exclusively dedicated to kernelspace would provide any mitigation against privelige escalation via rowhammer. Are we
by kibwen 8y ago
I wonder if having a separate stick of RAM exclusively dedicated to kernelspace would provide any mitigation against privelige escalation via rowhammer. Are we considering a future where every "ring" is literally a separate set of CPU, RAM, etc in order to stymie side channels, or is that just too crazy?
- ghthor 8y agoSounds good to me, would be fun to piece that together and pick different types of parts for each different function.
- paulryanrogers 8y agoIf kernel space were relatively small this might be practical as a motherboard feature, possibly soldered in place. Though I doubt it'll become standard unless there are no other alternatives since it seems like a very specialized solution.
- Insequent 8y agoThe kernel's memory usage is typically pretty small, unless you're considering the page cache to be part of it. Although: I once investigated a soft freeze on a realtime-patched Linux system that turned out to be caused by a vendor's software somehow managing to indefinitely stall an RCU grace period, eventually consuming all available memory on the system. The kernel core dump being over 4GB in size was a bit of a give-away.
- rocqua 8y agoThat would hurt VDSO wouldn't it?
- saati 8y agoWouldn't help against rowhammer via ethernet[1]. [1] https://www.cs.vu.nl/~herbertb/download/papers/throwhammer_atc18.pdf https://www.cs.vu.nl/~herbertb/download/papers/throwhammer_a...