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:
 * https://github.com/SELinuxProject/setools/issues/74

Version-Release number of selected component (if applicable):
python3-setools-4.3.0-3.el8.x86_64
setools-console-4.3.0-3.el8.x86_64

How reproducible:
 * always

Steps to Reproduce:
# echo "allowx init_t init_t ( ioctl unix_dgram_socket ( range 0x0000 0x00ff )))" > testpolicy.cil
# semodule -i testpolicy.cil
# sesearch --allowxperm

Actual results:
allowxperm init_t init_t:unix_dgram_socket ioctl 0x0000;

Expected results:
allowxperm init_t init_t:unix_dgram_socket ioctl 0x0000-0x00ff;

Additional info:
 * latest version of setools (4.4.1) fixes the problem

The same reproducer is used in both cases.

Not yet fixed version of sediff (RHEL-8.8):

# sediff --allowx ./policy /sys/fs/selinux/policy'
Allowxperm Rules (0 Added, 1 Removed, 0 Modified)
   Removed Allowxperm Rules: 1
      - allowxperm init_t init_t:unix_dgram_socket ioctl 0x0000;

Already fixed version of sediff (RHEL-9.2):

# sediff --allowx ./policy /sys/fs/selinux/policy'
Allowxperm Rules (0 Added, 1 Removed, 0 Modified)
   Removed Allowxperm Rules: 1
      - allowxperm init_t init_t:unix_dgram_socket ioctl 0x0000-0x00ff;

The problem is reproducible when the range starts with 0x0000. When the range starts with a higher number, both sesearch and sediff tools work correctly.

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 (setools 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-2023:7183