| Summary: | Use-after free in resolver in case the fd is writeable and readable at the same time | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | sssd | Assignee: | SSSD Maintainers <sssd-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Steeve Goveas <sgoveas> |
| Severity: | urgent | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | apeetham, ekeck, grajaiya, jhrozek, lslebodn, mkosek, mzidek, nsoman, pbrezina, sssd-maint, tscherf |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-1.14.0-43.el7_3.11 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if the socket that the System Security Services Daemon (SSSD) uses to communicate with the DNS server was writable and readable, and additionally an error occurred while processing the first event, SSSD accessed freed memory and the service terminated unexpectedly. A patch has been applied and SSSD now processes both events using the same resolver callback call. As a result, SSSD no longer fails in the described scenario.
|
Story Points: | --- |
| Clone Of: | 1400422 | Environment: | |
| Last Closed: | 2017-01-17 18:10:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1400422 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-12-13 15:57:34 UTC
Verified Sanity only on SSSD Version: sssd-1.14.0-43.el7_3.11 The automated regression round for the FAILOVER suite which covers the resolver code as well, was executed successfully on the upgraded sssd package: sssd-1.14.0-43.el7_3.11 See beaker job : https://beaker.engineering.redhat.com/jobs/1662438 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, 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://rhn.redhat.com/errata/RHBA-2017-0078.html |