In CVE-2017-0358, author notes that

The issue is that /sbin/modprobe is not designed to run in a setuid context. As the manpage of modprobe explicitly points out

The MODPROBE_OPTIONS environment variable can also be used
to pass arguments to modprobe.

modprobe is supposed to add/remove modules from kernel, which anyway requires root privileges.
So what does it mean to say that "modprobe is not designed to run in setuid context"?

  • The explanation is in the very next paragraph. – JdeBP Nov 5 '17 at 9:42
  • I understood the whole exploit. My question is, to run the modprobe, you need root privileges. How different is setting uid compared to using running it as sudo? – Jithin Pavithran Nov 5 '17 at 10:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.