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.

Description of problem:

In bug 2016038 we confirmed that zipl_vsyscall_argument SCAP rule should stay in RHEL 9 OSPP SCAP profile. Upon closer review and checking

    https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?highlight=vsyscall

which says

        vsyscall=       [X86-64]

the SCAP rule zipl_vsyscall_argument seems very unnecessary, given zipl is only used on s390x on RHEL, and likely on other OSes as well.

Please remove the zipl_vsyscall_argument SCAP rule from the RHEL 9 OSPP SCAP profile.

Consider removing it from all SCAP profiles shipped in the scap-security-guide, and potentially removing it altogether, unless there is some indication that zipl is used on x86_64 architecture on some of the OSes supported by https://github.com/ComplianceAsCode/content.

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

scap-security-guide-0.1.60-5.el9.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. On s390x, run
   # oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml

Actual results:

xccdf_org.ssgproject.content_rule_zipl_vsyscall_argument is listed.

Expected results:

xccdf_org.ssgproject.content_rule_zipl_vsyscall_argument is not listed.

Additional info:

a PR exists in https://github.com/ComplianceAsCode/content/pull/9083

https://github.com/ComplianceAsCode/content/pull/9083 has been merged to upstream

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 (scap-security-guide bug fix and enhancement update), 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/RHBA-2022:8131