CVE-2019-15325
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.26%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 1.26% probability · 70th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Affected
- galliumos/galliumos
- Source
- cve@mitre.org
EPSS 1.3% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://github.com/GalliumOS/galliumos-distro/issues/514Third Party Advisory
- https://www.kernel.org/doc/Documentation/security/Yama.txtThird Party Advisory
- https://github.com/GalliumOS/galliumos-distro/issues/514Third Party Advisory
- https://www.kernel.org/doc/Documentation/security/Yama.txtThird Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.