Skip to content(if available)orjump to list(if available)

Reviving the modprobe_path Technique: Overcoming search_binary_handler() Patch

ch33zer

Does anyone know why modprobe_path isn't in read only memory? Would just making it const char be enough to avoid this technique?

ch33zer

Oh, it's because it can be set by /proc/sys/kernel/modprobe