Bug 1689344

Summary: please add kptr_restrict=1 to /usr/lib/sysctl.conf/50-default.conf
Product: Red Hat Enterprise Linux 7 Reporter: Neil Horman <nhorman>
Component: systemdAssignee: David Tardon <dtardon>
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7CC: dtardon, jfarmer, systemd-maint-list
Target Milestone: rc   
Target Release: 7.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1689346 (view as bug list) Environment:
Last Closed: 2020-09-29 20:32:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neil Horman 2019-03-15 16:45:30 UTC
Description of problem:
In rhel6 the kernel defaulted the kptr_restrict sysctl value to 1 as a security measure (to prevent kernel addresses from being exposed in proc file and kernel logs).  Later upstream, the default was changed to 0 to allow for easier debugging of kernel trees, with the advice that distributions wanting the additional security should set this value to one using the sysctl service at boot time.  Given that RHEL would like to have this additional security for regular users, please set the kptr_restrict sysctl to the value 1 in the referenced sysctl file so that the systemd-sysctl service assigns it during boot.

Comment 2 David Tardon 2019-12-03 12:59:55 UTC
PR: https://github.com/systemd-rhel/rhel-7/pull/59

Comment 4 Lukáš Nykrýn 2020-04-27 13:18:30 UTC
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-7/pull/59

Comment 11 errata-xmlrpc 2020-09-29 20:32:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: systemd security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4007