---

ASA-202004-2 - log back

ASA-202004-2 edited at 01 Apr 2020 20:33:49

Workaround

- By default linux-hardened is safe as it restricts BPF access to privileged users. In case the kernel.unprivileged_bpf_disabled setting has been explicitly changed, it can be restricted again: + By default linux-hardened is safe as it restricts BPF access to + privileged users. In case the kernel.unprivileged_bpf_disabled setting + has been explicitly changed, it can be restricted again: # sysctl -w kernel.unprivileged_bpf_disabled=1

ASA-202004-2 edited at 01 Apr 2020 12:04:33

Workaround

- By default linux-hardened is safe as it restricts BPF access to privileged users. In case the kernel.unprivileged_bpf_disabled setting has been explicitly changed, it can be restricted again: + By default linux-hardened is safe as it restricts BPF access to privileged users. In case the kernel.unprivileged_bpf_disabled setting has been explicitly changed, it can be restricted again: # sysctl -w kernel.unprivileged_bpf_disabled=1

ASA-202004-2 edited at 01 Apr 2020 11:48:57
Workaround	+ By default linux-hardened is safe as it restricts BPF access to privileged users. In case the kernel.unprivileged_bpf_disabled setting has been explicitly changed, it can be restricted again: + + # sysctl -w kernel.unprivileged_bpf_disabled=1
Impact	+ An unprivileged local user or process can crash the kernel, resulting in a denial of service, or potentially gain root privileges on the system in case the default BPF access has been changed to allow unprivileged users.

ASA-202004-2 created at 01 Apr 2020 08:48:35