RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1438997 - SECCOMP records have wrong syscall
Summary: SECCOMP records have wrong syscall
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: audit
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Steve Grubb
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-05 00:46 UTC by Steve Grubb
Modified: 2017-08-01 20:53 UTC (History)
1 user (show)

Fixed In Version: audit-2.7.5-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:53:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2008 0 normal SHIPPED_LIVE audit bug fix update 2017-08-01 18:34:07 UTC

Description Steve Grubb 2017-04-05 00:46:53 UTC 
Description of problem:
It was discovered that when logging in the enriched mode, that the syscall being recorded was wrong: 

type=SECCOMP msg=audit(1491225059.340:568): auid=4325 uid=4325 gid=4325 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3297 comm="QtWebEngineProc" exe="/usr/lib64/qt5/libexec/QtWebEngineProcess" sig=0 arch=c000003e syscall=91 compat=0 ip=0x7f54f7524887 code=0x50000AUID="sgrubb" UID="sgrubb" GID="sgrubb" ARCH=x86_64 SYSCALL=unknown-syscall(-1)

This causes problems later because auparse favors the stored interpreted value rather than recalculate from scratch.


Version-Release number of selected component (if applicable):
audit-2.6.5

How reproducible:
Always
Comment 3 Steve Grubb 2017-04-10 15:08:01 UTC 
audit-2.7.5-1.el7 was built to resolve this issue.
Comment 5 Ondrej Moriš 2017-04-27 10:09:53 UTC 
Successfully reproduced and verified on all supported architectures

OLD (audit-2.6.5-3.el7_3.1)
===========================
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: resolve syscall name using -i [ENRICHED]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [  BEGIN   ] :: Running 'ausearch -ts "20:09:46" -m SECCOMP -i &>log'
:: [   PASS   ] :: Command 'ausearch -ts "20:09:46" -m SECCOMP -i &>log' (Expected 0, got 0)
:: [   FAIL   ] :: File 'log' should contain ' syscall=exit_group' 
----
type=SECCOMP msg=audit(04/26/2017 20:09:46.042:116) : auid=unset uid=root gid=root ses=unset subj=system_u:unconfined_r:unconfined_t:s0 pid=10518 comm=repro sig=SIGSYS arch=x86_64 syscall=unknown compat=0 ip=0x7f7905f7f9c9 code=kill 
'2eb6da30-2d5f-4392-86c9-7bdce4cbc795'
resolve-syscall-name-using-i-ENRICHED- result: FAIL


NEW (audit-2.7.6-1.el7)
=======================
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: resolve syscall name using -i [ENRICHED]
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [  BEGIN   ] :: Running 'ausearch -ts "20:12:49" -m SECCOMP -i &>log'
:: [   PASS   ] :: Command 'ausearch -ts "20:12:49" -m SECCOMP -i &>log' (Expected 0, got 0)
:: [   PASS   ] :: File 'log' should contain ' syscall=exit_group' 
'd818a18c-440c-415b-a04f-dc34b6038ae9'
resolve-syscall-name-using-i-ENRICHED- result: PASS

For more details please see TJ#1827515.
Comment 6 errata-xmlrpc 2017-08-01 20:53:38 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://access.redhat.com/errata/RHEA-2017:2008
Note You need to log in before you can comment on or make changes to this bug.