Bad posix clock speculation mitigation backport
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Tyler Hicks |
Bug Description
[Impact]
Vitaly Nikolenko pointed out that syscall(
https:/
[Test Case]
Execute the following test program and verify that it prints out "clock_gettime: Invalid argument" rather than triggering a NULL pointer dereference and stack trace in the kernel logs.
==========
#include <stdio.h>
#include <time.h>
int main(void)
{
int rc = clock_gettime(10, 0);
if (rc < 0)
return rc;
}
==========
[Regression Potential]
Low. The fix is easy to review and fixes a denial of service issue that's trivial to trigger.
Changed in linux (Ubuntu Xenial): | |
status: | New → In Progress |
assignee: | nobody → Tyler Hicks (tyhicks) |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | In Progress → Invalid |
assignee: | Tyler Hicks (tyhicks) → nobody |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Fix submitted: https:/ /lists. ubuntu. com/archives/ kernel- team/2019- October/ 104582. html