Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2019887

Summary:	Update to 2.5.2 or newer
Product:	Red Hat Enterprise Linux 9	Reporter:	Debarshi Ray <debarshir>
Component:	libseccomp	Assignee:	Zoltan Fridrich <zfridric>
Status:	CLOSED ERRATA	QA Contact:	Martin Zelený <mzeleny>
Severity:	high	Docs Contact:	Jan Fiala <jafiala>
Priority:	high
Version:	9.0	CC:	dapospis, mjahoda, mzeleny, rsroka, tpopela, zfridric
Target Milestone:	rc	Keywords:	Rebase, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libseccomp-2.5.2-2.el9	Doc Type:	Enhancement
Doc Text:	.`libseccomp` provided in version 2.5.2 RHEL 9.0 provides the `libseccomp` packages in upstream version 2.5.2. This version provides many bug fixes and enhancements over previous versions, most notably: * Updated the syscall table for Linux to version `v5.14-rc7`. * Added the `get_notify_fd()` function to the Python bindings to get the notification file descriptor. * Consolidated multiplexed syscall handling for all architectures into one location. * Added multiplexed syscall support to the PowerPC (PPC) and MIPS architectures. * Changed the meaning of the `SECCOMP_IOCTL_NOTIF_ID_VALID` operation within the kernel. * Changed the `libseccomp` file descriptor notification logic to support the kernel's previous and new usage of `SECCOMP_IOCTL_NOTIF_ID_VALID`. * Fixed a bug where `seccomp_load()` could only be called once. * Changed the notification `fd` handling to only request a notification `fd` if the filter has a `_NOTIFY` action. * Added documentation about `SCMP_ACT_NOTIFY` to the `seccomp_add_rule(3)` manpage. * Clarified the maintainers’ GPG keys.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:56:03 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 Debarshi Ray 2021-11-03 14:40:31 UTC

Currently, RHEL 9 has libseccomp-2.5.0 which doesn't know about system calls added to recent versions of the Linux kernel.

For example, I see these commits after 2.5.0:

  syscalls: update the syscall table to v5.12-rc7 
  https://github.com/seccomp/libseccomp/commit/c56a00fe173a7dd5

  syscalls: add close_range() syscall 
  https://github.com/seccomp/libseccomp/commit/ac849e7960547d41

  syscalls: update to Linux v5.14-rc7
  https://github.com/seccomp/libseccomp/commit/c3559610ffdcda23

I see that the CentOS Stream dist-git has Linux 5.14.0 and I see corresponding builds in Brew, so this seems relevant.

I noticed this while working on fixing CVE-2021-41133 (bug 2012245) for Flatpak, both upstream and for Fedora and RHEL.

In certain situations, Flatpak receives -EFAULT from seccomp_rule_add() if libseccomp doesn't know about the system call.  To avoid user-visible breakage, Flatpak ignores that and keeps going.  However, if the user is running a kernel that's new enough to have that system call, then this means that Flatpak doesn't block the call, leaving a gap in its sandbox.

Having a newer libseccomp will make our lives easier when evaluating the security impact and fixes for the next CVE that rolls in, by reducing the number of different kernel/libseccomp combinations.

Updating from 2.5.0 to 2.5.2 should be pretty safe, and we now have similar updates for Fedora >= 33.

Comment 1 Debarshi Ray 2021-11-03 14:44:43 UTC

Note that RHEL 8 already has libseccomp-2.5.1 (bug 1927635) since RHEL 8.4.  So, currently, RHEL 8 is shipping newer code than RHEL 9.  :)

Comment 3 Debarshi Ray 2021-11-05 10:43:31 UTC

Thanks for working on this!

Comment 12 errata-xmlrpc 2022-05-17 15:56:03 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 (new packages: libseccomp), 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-2022:3969