That kind of attack is not possible with a signed kernel module/driver.

How is using a compromised userspace library not possible with a signed kernel module?

That aside, if the events would unfold similarly, the software requiring to be signed would be, in fact, signed.

An awfully stupid comment TBF. As if you desperately tried to defend MS.