2 ms·
A driver should only be a security issue if it's actually running (loaded), and even if you have the module available on disk (which again, is unlikely for some
by yjftsjthsd-h 6y ago
A driver should only be a security issue if it's actually running (loaded), and even if you have the module available on disk (which again, is unlikely for something obscure enough) it'll only get loaded if the kernel detects hardware that uses it, or someone does a modprobe (or equivalent), which already requires root. So having the driver available shouldn't add any risk unless you actually are using it anyways.
- swiley 6y agoI was under the impression the driver has to be loaded before the kernel can detect if it can use the hardware (that’s how probing works) so it’s the user space that picks the modules to load. Of course the driver probably won’t do anything if it never gets attached to a device (other than responding to probe requests on the bus it uses.)