Linux 6.19 Will Allow Enforcing IPE Security Checks On Indirectly Executed Scripts
([Linux Security] 6 Hours Ago
Integrity Policy Enforcement (IPE))
- Reference: 0001596793
- News link: https://www.phoronix.com/news/Linux-6.19-IPE-AT_EXECVE_CHECK
- Source link:
Linux's [1]Integrity Policy Enforcement "IPE" module is gaining a useful addition with the in-development [2]Linux 6.19 kernel.
The Linux Integrity Policy Enforcement now honors the "AT_EXECVE_CHECK" flag so user-space interpreters can signal to the kernel to perform IPE security checks on script files before execution. This functionality with AT_EXECVE_CHECK extends IPE enforcement now to indirectly-executed scripts on the system.
The updated Linux IPE documentation further explains of the new AT_EXECVE_CHECK behavior for scripts:
"With the introduction of the AT_EXECVE_CHECK flag, interpreters can use it to signal the kernel that a script file will be executed, and request the kernel to perform LSM security checks on it.
IPE's EXECUTE operation enforcement differs between compiled executables and interpreted scripts: For compiled executables, enforcement is triggered automatically by the kernel during execve(), execveat(), mmap() and mprotect() syscalls when loading executable content. For interpreted scripts, enforcement requires explicit interpreter integration using execveat() with AT_EXECVE_CHECK flag. Unlike exec syscalls that IPE intercepts during the execution process, this mechanism needs the interpreter to take the initiative, and existing interpreters won't be automatically supported unless the signal call is added."
This security contribution from Microsoft's Linux team extends IPE enforcement to indirectly executed scripts so that trusted scripts can execute while denying untrusted scripts.
More details for those interested via the [3]IPE merge for the Linux 6.19 kernel.
[1] https://www.phoronix.com/news/Linux-6.12-IPE-LSM-Security
[2] https://www.phoronix.com/search/Linux+6.19
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c8321831480d80af01ce001bd6626fc130fd13b1
The Linux Integrity Policy Enforcement now honors the "AT_EXECVE_CHECK" flag so user-space interpreters can signal to the kernel to perform IPE security checks on script files before execution. This functionality with AT_EXECVE_CHECK extends IPE enforcement now to indirectly-executed scripts on the system.
The updated Linux IPE documentation further explains of the new AT_EXECVE_CHECK behavior for scripts:
"With the introduction of the AT_EXECVE_CHECK flag, interpreters can use it to signal the kernel that a script file will be executed, and request the kernel to perform LSM security checks on it.
IPE's EXECUTE operation enforcement differs between compiled executables and interpreted scripts: For compiled executables, enforcement is triggered automatically by the kernel during execve(), execveat(), mmap() and mprotect() syscalls when loading executable content. For interpreted scripts, enforcement requires explicit interpreter integration using execveat() with AT_EXECVE_CHECK flag. Unlike exec syscalls that IPE intercepts during the execution process, this mechanism needs the interpreter to take the initiative, and existing interpreters won't be automatically supported unless the signal call is added."
This security contribution from Microsoft's Linux team extends IPE enforcement to indirectly executed scripts so that trusted scripts can execute while denying untrusted scripts.
More details for those interested via the [3]IPE merge for the Linux 6.19 kernel.
[1] https://www.phoronix.com/news/Linux-6.12-IPE-LSM-Security
[2] https://www.phoronix.com/search/Linux+6.19
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c8321831480d80af01ce001bd6626fc130fd13b1