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.
Bug 627901 - Segfault when decoding DMI data in dmi_processor_id()
Summary: Segfault when decoding DMI data in dmi_processor_id()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-dmidecode
Version: 6.1
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Roman Rakus
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 726613 726614
TreeView+ depends on / blocked
 
Reported: 2010-08-27 10:56 UTC by Roman Rakus
Modified: 2014-01-13 00:12 UTC (History)
15 users (show)

Fixed In Version: python-dmidecode-3.10.13-1.el6
Doc Type: Bug Fix
Doc Text:
Previously, certain DMI (Direct Media Interface) tables did not report CPU information as a string and returned the NULL value instead. Consequently, Python terminated unexpectedly with a segmentation fault when trying to identify the CPU type by performing a string comparison. With this update, additional checks for NULL values, performed prior the string comparison, have been added to the code, thus fixing this bug.
Clone Of: 596264
Environment:
Last Closed: 2011-12-06 11:51:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1589 0 normal SHIPPED_LIVE python-dmidecode bug fix update 2011-12-06 00:38:47 UTC

Comment 3 Roman Rakus 2011-06-29 16:33:56 UTC 
Fixed in python-dmidecode-3.10.13-1.el6
Comment 4 Roman Rakus 2011-07-07 12:19:56 UTC 
Proposed for z-streams based on request from Matthew Whitehead
Comment 6 Eliska Slobodova 2011-07-25 14:58:45 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When trying to identify the processor type by performing a string comparison, Python terminated with a segmentation fault. This was caused by DMI tables which did not report the CPU processor information as a string and returned a NULL value instead. This update adds additional checks for NULL values before doing the string comparison.
Comment 9 Tomas Capek 2011-08-03 14:56:37 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When trying to identify the processor type by performing a string comparison, Python terminated with a segmentation fault. This was caused by DMI tables which did not report the CPU processor information as a string and returned a NULL value instead. This update adds additional checks for NULL values before doing the string comparison.+Previously, certain DMI (Direct Media Interface) tables did not report CPU information as a string and returned the NULL value instead. Consequently, Python terminated unexpectedly with a segmentation fault when trying to identify the CPU type by performing a string comparison. With this update, additional checks for NULL values, performed prior the string comparison, have been added to the code, thus fixing this bug.
Comment 10 David Sommerseth 2011-08-03 15:14:25 UTC 
(In reply to comment #9)
>     Technical note updated. If any revisions are required, please edit the
> "Technical Notes" field
>     accordingly. All revisions will be proofread by the Engineering Content
> Services team.
> 
>     Diffed Contents:
> @@ -1 +1 @@
> -When trying to identify the processor type by performing a string comparison,
> Python terminated with a segmentation fault. This was caused by DMI tables
> which did not report the CPU processor information as a string and returned a
> NULL value instead. This update adds additional checks for NULL values before
> doing the string comparison.+Previously, certain DMI (Direct Media Interface)
> tables did not report CPU information as a string and returned the NULL value
> instead. Consequently, Python terminated unexpectedly with a segmentation fault
> when trying to identify the CPU type by performing a string comparison. With
> this update, additional checks for NULL values, performed prior the string
> comparison, have been added to the code, thus fixing this bug.


Just a heads up, the DMI abbreviation is wrong.  From the man page of dmidecode:

       dmidecode  is  a tool for dumping a computer's DMI (some say
       SMBIOS) table contents in a human-readable format.
       [...snip...]

       SMBIOS stands for System Management BIOS, while  DMI  stands
       for Desktop Management Interface. Both standards are tightly
       related and developed by the DMTF (Desktop  Management  Task
       Force).
Comment 12 errata-xmlrpc 2011-12-06 11:51:40 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2011-1589.html
Note You need to log in before you can comment on or make changes to this bug.