kill incorrectly parses negative PIDs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
procps (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
dann frazier |
Bug Description
[Impact]
When kill is called with a negative argument, incorrect parsing can lead it to call sys_kill(-1), thus sending a signal to all permitted processes on the system. A couple of users have hit this while deploying Hadoop, which seems to tickle this - basically killing everything on the system.
[Test Case]
Though I don't know what Hadoop is calling, here's a couple of ways to trigger this:
One possibility is if kill were called w/ a numeric signal that
happened to start with a '1' and while omitting the required <pid>
argument:
kill -12
Another would be to specify a numeric signal (that again happened to
start with a 1) multiple times:
kill -13 -13 12345
[Regression Risk]
This is a backport from upstream that is already available in 16.10, with no known regressions.
Changed in procps (Ubuntu): | |
status: | New → Fix Released |
Changed in procps (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → dann frazier (dannf) |
tags: |
added: verification-failed removed: verification-needed |
Changed in procps (Ubuntu): | |
importance: | Undecided → High |
Confirmed fixed in yakkety/zesty.