Bug 2049300
Summary: | SELinux is preventing /usr/bin/rpcbind from 'name_bind' accesses on the udp_socket port 65154. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bruce Petrie <bitflip10> |
Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 35 | CC: | dwalsh, grepl.miroslav, lvrabec, mmalik, omosnace, pkoncity, quintela, vmojzis, zpytela |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:353bb6bd6a8e04006146647683af50286d24b157900427787a028d67f4c84d5a; | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-22 10:25:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bruce Petrie
2022-02-01 21:27:10 UTC
Similar problem has been detected: It happened during boot after 1st installation. I only use rpcbind because it is needed for nfs-server.service, nothing related to nis here. hashmarkername: setroubleshoot kernel: 5.16.9-200.fc35.x86_64 package: selinux-policy-targeted-35.15-1.fc35.noarch reason: SELinux is preventing rpcbind from 'name_bind' accesses on the udp_socket port 64585. type: libreport Has something changed in your configuration? Processes are allowed to bind to ephemeral ports when the port number matches the range for local ports as defined in the net.ipv4.ip_local_port_range kernel tunable, regardless of their SELinux label: # sysctl net.ipv4.ip_local_port_range net.ipv4.ip_local_port_range = 32768 60999 Refer to a knowledgebase article for more details (subscription required): https://access.redhat.com/solutions/3236651 (In reply to Zdenek Pytela from comment #2) > Has something changed in your configuration? Processes are allowed to bind > to ephemeral ports when the port number matches the range for local ports as > defined in the net.ipv4.ip_local_port_range kernel tunable, regardless of > their SELinux label: > > # sysctl net.ipv4.ip_local_port_range > net.ipv4.ip_local_port_range = 32768 60999 Hi again, thank you for looking into this. The SELinux errors do not occur every system boot but do occur often enough to be annoying. The system I am seeing this on is an older laptop with very boring software requirements that has been upgraded over many fedora releases (FC19 to FC35). A much faster server running security camera software, multiple network interfaces, multiple disk volumes, etc does not seems to exhibit this behavior. So is this a cockpit error on this laptop or something else... The ephemeral port number involved has varied over time. I have no need for NIS or NFS and have tried to avoid running since they expose more attack vectors. I saw this behavior occasionally on fc34 as well as now on fc35. # sysctl net.ipv4.ip_local_port_range net.ipv4.ip_local_port_range = 32768 60999 # getsebool -a|grep nis_enabled nis_enabled --> off I removed the only SELinux module that I installed to eliminate that as a possibility. I will report back after testing for a week or so unless there is anything else you would like to be tested. cheers > > Refer to a knowledgebase article for more details (subscription required): > https://access.redhat.com/solutions/3236651 (In reply to Bruce Petrie from comment #3) > Hi again, thank you for looking into this. The SELinux errors do not occur > every system boot but do occur often enough to be annoying. The system I am > seeing this on is an older laptop with very boring software requirements > that has been upgraded over many fedora releases (FC19 to FC35). A much > faster server running security camera software, multiple network interfaces, > multiple disk volumes, etc does not seems to exhibit this behavior. So is > this a cockpit error on this laptop or something else... > > The ephemeral port number involved has varied over time. I have no need for > NIS or NFS and have tried to avoid running since they expose more attack > vectors. I saw this behavior occasionally on fc34 as well as now on fc35. I don't think the range changed in past few years, but some programs may follow different standards. Can you affect the range rpcbind can bind to? > # sysctl net.ipv4.ip_local_port_range > net.ipv4.ip_local_port_range = 32768 60999 > > # getsebool -a|grep nis_enabled > nis_enabled --> off > > I removed the only SELinux module that I installed to eliminate that as a > possibility. > > I will report back after testing for a week or so unless there is anything > else you would like to be tested. If the occurence is more like random, it would probably need attention of rpcbind developers. Closing a dup of bz#1758147 to continue the discussion there. *** This bug has been marked as a duplicate of bug 1758147 *** |