precise has wrong PTRACE_EVENT_SECCOMP value
Bug #1326905 reported by
Kees Cook
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
In v3.2, there was confusion over the new "PTRACE_EVENT_EXIT" value. Ultimately, upstream fixed it, but in the precise backporting of seccomp, the wrong value was used: 5cdf389aee90109
As a result, seccomp filteres expecting ptrace managers don't work correctly on precise.
The attached patch backports the upstream PTRACE_EVENT_EXIT value and restores the correct PTRACE_
SRU Justification:
Impact: seccomp filters using ptrace managers don't work on precise
Fix: fix ptrace flag numbering to match all other released kernel versions
Testcase: https:/
Wrong:
$ cd /src/kernels/ ubuntu/ precise ; git grep PTRACE_ EVENT_SECCOMP linux/ptrace. h:#define PTRACE_ EVENT_SECCOMP 8
...
include/
Correct:
$ cd /src/kernels/ ubuntu/ trusty ; git grep PTRACE_ EVENT_SECCOMP uapi/linux/ ptrace. h:#define PTRACE_ EVENT_SECCOMP 7
...
include/