> Wait, Windows exports kernel address to userspace?! Dont know about these particular calls. But info leaks where a kernel address is leaked are apparently qu

> Wait, Windows exports kernel address to userspace?! Dont know about these particular calls. But info leaks where a kernel address is leaked are apparently quite common. They're usually fixed when found. But this is the reason OpenBSD relinks the kernel every boot in a random order. [0] Its's too easy to leak a pointer and invalidate KASLR, because now you can calculate the KASLR offset. The 'well known' part does seem a bit weird though. [0] https://security.stackexchange.com/questions/163565/openbsd-is-implementing-karl-how-does-this-improve-security https://security.stackexchange.com/questions/163565/openbsd-... Edit: https://github.com/sam-b/windows_kernel_address_leaks/blob/master/notes/gSharedInfo.md https://github.com/sam-b/windows_kernel_address_leaks/blob/m... Seems windows patches them too, sometimes. Checking the rest of the repo they don't seem to care much though.