Bug 1241585

Summary: BUG: libseccomp has multiple problems relating to x86_64 and syscall argument filtering
Product: Red Hat Enterprise Linux 7 Reporter: Paul Moore <pmoore>
Component: libseccompAssignee: Paul Moore <pmoore>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: chayang, huding, juzhang, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libseccomp-2.3.1-0.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 03:29:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Moore 2015-07-09 14:21:35 UTC
Description of problem:
There is a new upstream release of libseccomp, v2.2.3 or later, which fixes multiple problems relating to x86_64/x32 as well as issues with syscall argument filtering.

Version-Release number of selected component (if applicable):
All released versions of libseccomp on RHEL7.

Additional info:

 -> https://github.com/seccomp/libseccomp/releases

Comment 1 Paul Moore 2015-07-09 14:23:06 UTC
As a FYI, updated libseccomp packages have already been submitted for Rawhide, F22, and F21.

Comment 2 Paul Moore 2016-02-29 21:47:14 UTC
New libseccomp upstream release, v2.3.0, resolves this issue.  A RHEL-7.3 build will be available soon.

 * https://github.com/seccomp/libseccomp/releases/tag/v2.3.0

Comment 3 Paul Moore 2016-04-20 22:20:43 UTC
This should be resolved in libseccomp-2.3.1-0.el7 which is now available in the RHEL-7.3 branch.

Comment 7 errata-xmlrpc 2016-11-04 03:29:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2310.html