Kernel panic on oops
An XCCDF Rule
Description
To set the runtime status of the kernel.panic_on_oops
kernel parameter, run the following command:
$ sudo sysctl -w kernel.panic_on_oops=1To make sure that the setting is persistent, add the following line to a file in the directory
/etc/sysctl.d
: kernel.panic_on_oops = 1
warning alert: Functionality Warning
The system may start to panic when it normally wouldn't. A non-catastrophic error that
would have allowed the system to continue operating will now result in a panic.
Rationale
An attacker trying to exploit the kernel may trigger kernel OOPSes, panicking the system will impede them from continuing.
- ID
- xccdf_org.ssgproject.content_rule_sysctl_kernel_panic_on_oops
- Severity
- Medium
- References
- Updated
Remediation - Ansible
- name: List /etc/sysctl.d/*.conf files
find:
paths:
- /etc/sysctl.d/
- /run/sysctl.d/
- /usr/local/lib/sysctl.d/
Remediation - Shell Script
# Remediation is applicable only in certain platforms
if [ ! -f /.dockerenv ] && [ ! -f /run/.containerenv ]; then
# Comment out any occurrences of kernel.panic_on_oops from /etc/sysctl.d/*.conf files
for f in /etc/sysctl.d/*.conf /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf; do