kernel-packages team mailing list archive

[Kees Cook <kees@xxxxxxxxxx>]

Public bug reported:

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:
5cdf389aee90109e2e3d88085dea4dd5508a3be7

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_EVENT_SECCOMP value.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

** Affects: linux (Ubuntu Precise)
     Importance: Undecided
         Status: Incomplete


** Tags: precise

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1326905

Title:
  precise has wrong PTRACE_EVENT_SECCOMP value

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” source package in Precise:
  Incomplete

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:
  5cdf389aee90109e2e3d88085dea4dd5508a3be7

  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_EVENT_SECCOMP value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326905/+subscriptions