diff options
| author | David Howells <dhowells@redhat.com> | 2019-08-20 03:17:57 +0300 |
|---|---|---|
| committer | James Morris <jmorris@namei.org> | 2019-08-20 07:54:16 +0300 |
| commit | 02e935bf5b34edcc4cb0dc532dd0e1a1bfb33b51 (patch) | |
| tree | d1029d3f5dccd6dbba74b1d0b445fa2b5ee4ffb4 /security/lockdown | |
| parent | 906357f77a077508d160e729f917c5f0a4304f25 (diff) | |
| download | linux-02e935bf5b34edcc4cb0dc532dd0e1a1bfb33b51.tar.xz | |
lockdown: Lock down /proc/kcore
Disallow access to /proc/kcore when the kernel is locked down to prevent
access to cryptographic data. This is limited to lockdown
confidentiality mode and is still permitted in integrity mode.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Matthew Garrett <mjg59@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'security/lockdown')
| -rw-r--r-- | security/lockdown/lockdown.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c index 2eadbe0667e7..403b30357f75 100644 --- a/security/lockdown/lockdown.c +++ b/security/lockdown/lockdown.c @@ -31,6 +31,7 @@ static char *lockdown_reasons[LOCKDOWN_CONFIDENTIALITY_MAX+1] = { [LOCKDOWN_MODULE_PARAMETERS] = "unsafe module parameters", [LOCKDOWN_MMIOTRACE] = "unsafe mmio", [LOCKDOWN_INTEGRITY_MAX] = "integrity", + [LOCKDOWN_KCORE] = "/proc/kcore access", [LOCKDOWN_CONFIDENTIALITY_MAX] = "confidentiality", }; |