In GalliumOS 3.0, CONFIG_SECURITY_YAMA is disabled but /etc/sysctl.d/10-ptrace.conf tries to set /proc/sys/kernel/yama/ptrace_scope to 1, which might increase risk because of the appearance that a protection mechanism is present when actually it is not.
References
Link | Resource |
---|---|
https://github.com/GalliumOS/galliumos-distro/issues/514 | Third Party Advisory |
https://www.kernel.org/doc/Documentation/security/Yama.txt | Third Party Advisory |
https://github.com/GalliumOS/galliumos-distro/issues/514 | Third Party Advisory |
https://www.kernel.org/doc/Documentation/security/Yama.txt | Third Party Advisory |
Configurations
History
21 Nov 2024, 04:28
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/GalliumOS/galliumos-distro/issues/514 - Third Party Advisory | |
References | () https://www.kernel.org/doc/Documentation/security/Yama.txt - Third Party Advisory |
Information
Published : 2019-08-22 20:15
Updated : 2024-11-21 04:28
NVD link : CVE-2019-15325
Mitre link : CVE-2019-15325
CVE.ORG link : CVE-2019-15325
JSON object : View
Products Affected
galliumos
- galliumos
CWE