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.

Description of problem:
systemd was recently patched for CVE-2021-33910 in RHEL 8.  That patch does not appear to be part of systemd in CentOS Stream 8.


Version-Release number of selected component (if applicable):
systemd-239-48.el8


Additional info:
CentOS Stream 8 can build the update once it's exported to git.centos.org.  To trigger that, please update systemd in the rhel-8.5.0 branch and attach the resulting build to 8.5 errata.

*** This bug has been marked as a duplicate of bug 1974700 ***

(In reply to Josh Boyer from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 1974700 ***

Please don't close tickets in favor of private ones. It makes it look like you're hiding something. I would hope that is not the intent. Either close the private ticket in favor of this one or make bug 1974700 public.

(In reply to Neal Gompa from comment #2)
> (In reply to Josh Boyer from comment #1)
> > 
> > *** This bug has been marked as a duplicate of bug 1974700 ***
> 
> Please don't close tickets in favor of private ones. It makes it look like
> you're hiding something. I would hope that is not the intent. Either close
> the private ticket in favor of this one or make bug 1974700 public.

No intention to hide anything.  The work is being done against 1974700 per our process.  Creating this bug isn't going to make it go faster or provide more information and just creates busywork for the team that's already trying to get fixes out across all RHEL releases.  I'll leave it to the team owning the issue to determine if 1974700 can be opened.