Bug 2369545
| Summary: | SELinux execmem access denial on startup | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | overact_ninetieth160 |
| Component: | fail2ban | Assignee: | Orion Poplawski <orion> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | anon.amish, hobbes1069, orion |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Description of problem: The following SELinux denial is logged several times upon startup of fail2ban: type=AVC msg=audit(1748686317.733:34516): avc: denied { execmem } for pid=785523 comm="grep" scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:system_r:fail2ban_t:s0 tclass=process permissive=0 How reproducible: Steps to Reproduce: 1. systemctl start fail2ban 2. Check audit log Additional info: I am not sure what fail2ban does that it wants execmem, so this might be an upstream issue.