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.
Thank you very much for providing the verbose logs.
From the logs we can see that the problem is triggered by rules "no_files_unowned_by_user" and "file_permissions_ungroupowned".
The rule "no_files_unowned_by_user" checks whether there aren't any files on the whole systems that are owned by invalid or not existing users. Check the detailed description of the rule at https://github.com/ComplianceAsCode/content/blob/master/linux_os/guide/system/permissions/files/no_files_unowned_by_user/rule.yml or in the HTML guide for the CIS profile. It seems that OpenSCAP has found a very large amount of files that are owned by invalid or unknown user and tries to collect information about them so that they could be shown in the report. However, there is too much of them that it hits the memory limits. From the logs, I can see that these files are located in /home/m525017/backups/ on your system but may be elsewhere as well.
The rule "file_permissions_ungroupowned" is similar but it checks for files that are group-owned by a group that doesn't exist (it isn't in /etc/groups). Check the detailed description in https://github.com/ComplianceAsCode/content/blob/master/linux_os/guide/system/permissions/files/file_permissions_ungroupowned/rule.yml or in the HTML guide for the CIS profile. A similar situation happens again, from the logs it seems that the system contains many files that are detected as offending this rule.
As a workaround, you can disable these 2 rules ("no_files_unowned_by_user" and "file_permissions_ungroupowned") by a tailoring file. The tailoring file can be created using scap-workbench, or using the autotailor command. Then you pass the tailoring file to oscap and you scan your customized profile instead of CIS profile. See for example https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/scanning-the-system-for-configuration-compliance-and-vulnerabilities_security-hardening#customizing-a-security-profile-with-scap-workbench_scanning-the-system-with-a-customized-profile-using-scap-workbench .
Another workaround would be to fix the ownership and groupownership of all the files in your filesystem and make sure that they're owned by valid and existing users and groups. You can find them using `sudo find / -nouser` and `sudo find / -nogroup`.