GNU bug report logs - #58891
LKRG blocks modprobe due to hardcoded paths

Previous Next

To reply to this bug, email your comments to 58891 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: DonaldSanders1968 <DonaldSanders1968 <at> protonmail.ch>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: LKRG blocks modprobe due to hardcoded paths
Date: Sun, 30 Oct 2022 04:51:16 +0000

[Message part 1 (text/plain, inline)]

Hi Guix,

LKRG with default config on Guix system will resist executing modprobe. Its log message is like:

Oct 30 xx:xx:xx localhost vmunix: [ 2534.269558] LKRG: ALERT: BLOCK: UMH: Executing program name /gnu/store/fas8d76ws2xsdaiiyv822qy3tjx2an6x-modprobe

I found it is caused by hardcoded modprobe path in [src/modules/exploit_detection/syscalls/p_call_usermodehelper/p_call_usermodehelper.c](https://github.com/lkrg-org/lkrg/blob/main/src/modules/exploit_detection/syscalls/p_call_usermodehelper/p_call_usermodehelper.c), which includes a whitelist for UMH validation in LKRG.

Kind regards,
Don

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.