Bug 1431702
| Summary: | python-dmidecode segfaults when reading invalid dmidecode data | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | python-dmidecode | Assignee: | Petr Oros <poros> |
| Status: | CLOSED ERRATA | QA Contact: | Mike Gahagan <mgahagan> |
| Severity: | medium | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | high | ||
| Version: | 7.2 | CC: | danken, dpinkert, poros, vslavik |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-dmidecode-3.10.13-12.el7_3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the dmidecode Python module did not check for presence of entries in the Desktop Management Interface (DMI) table and was unable to handle malformed data when querying the DMI table. As a consequence, when querying a non-existent or invalid DMI table entry, the dmidecode module terminated unexpectedly with a segmentation fault. This update adds a check for the presence and format of the DMI table entries. As a result, the dmidecode module no longer terminates with a segmentation fault when querying malformed DMI tables, and correctly returns empty data in the described situation.
|
Story Points: | --- |
| Clone Of: | 1385410 | Environment: | |
| Last Closed: | 2017-06-28 17:00:58 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: | |||
| Bug Depends On: | 1385410 | ||
| Bug Blocks: | |||
|
Description
Jaroslav Reznik
2017-03-13 16:02:38 UTC
Confirmed python-dmidecode-3.10.13-12.el7_3 is properly working with the provided reproducer image. 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://access.redhat.com/errata/RHBA-2017:1611 |