Re:Driver Signing changes in Windows 10, version 1607
by gtirloni on Tuesday August 02, 2016 @09:14AM
(#12209666)
Once malicious code gets into the kernel address space, the sky is the limit. I don't think it matters if there has been one or a million occurrences of kernel-space malware.
Look for more details on "ModPOS" for a particularly disastrous one.
Also, have there been many instances of malware in device drivers recently that would require a tightening up of the rules?
[0]: Microsoft's user-mode USB driver, which did (IIRC) need a signed .inf file but you didn't need to submit it for validation since all the actual code was Microsoft's (https://msdn.microsoft.com/en-gb/library/windows/hardware/ff...)