uu_kill
Affected
- introduced
0, fixed0.6.0(semver)
Fixed versions
0.6.0
Fix
- Fixed version
0.6.0cargo update -p uu_kill --precise 0.6.0
Advisory
Also known as: CVE-2026-35369
kill: 'kill -1' parsed as PID -1, sending SIGTERM to all processes (system crash / DoS)
kill -1 is incorrectly parsed as a positional pid = -1; combined with the default SIGTERM this calls kill(-1, SIGTERM), signaling nearly every process the caller can see. GNU kill recognizes -1/-9 as signals and reports "not enough arguments".
$ kill -1 # uutils: kill(-1, SIGTERM) -> mass termination / crash
$ kill -1 # GNU: kill: not enough arguments
Impact: a user running kill -1 mass-terminates processes, potentially crashing the system. Recommendation: parse -N as a signal number, and error with "not enough arguments" when no PID is given.
Remediation: Acknowledged by Canonical; fixed in commit cae94028.
---
_Reported by Zellic in the *uutils coreutils Program Security Assessment* (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.70. Credit: Zellic._
Medium Basis: The source's own band: MODERATE
0, fixed 0.6.0 (semver)0.6.0
0.6.0cargo update -p uu_kill --precise 0.6.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0