4 ms·
while not root cause, wouldn’t a module having corrupted memory still be an issue with either the OS (for not protecting it) or the module (for not sanitizing i
by mysterydip 4mo ago
while not root cause, wouldn’t a module having corrupted memory still be an issue with either the OS (for not protecting it) or the module (for not sanitizing input)?
- arcfour 4mo agoNo, because this would be kernel level code, so anything else running in the kernel (other drivers) could stomp on your memory and you couldn't do anything about it. No OS protections here.
- mysterydip 4mo agoAh that makes sense, thanks!