Red Hat Bugzilla – Full Text Bug Listing
|Summary:||[RHEL4.8] igb driver doesn't allocate enough buffer for ethtool_get_strings() [rhel-4.8.z]|
|Product:||Red Hat Enterprise Linux 4||Reporter:||RHEL Product and Program Management <pm-rhel>|
|Component:||kernel||Assignee:||Vitaly Mayatskikh <vmayatsk>|
|Status:||CLOSED ERRATA||QA Contact:||Red Hat Kernel QE team <kernel-qe>|
|Version:||4.8||CC:||bobby.suber, daniel_frazier, dannf, david.graham, dhoward, emcnabb, peterm, pm-eus, sandy.garza, sassmann|
|Fixed In Version:||Doc Type:||Bug Fix|
The data buffer ethtool_get_strings() allocated, for the igb driver, was smaller than the amount of data that was copied in igb_get_strings(), because of a miscalculation in IGB_QUEUE_STATS_LEN, resulting in memory corruption. This bug could have led to a kernel panic.
|Last Closed:||2009-10-22 11:09:51 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||517329|
Description RHEL Product and Program Management 2009-09-11 05:17:07 EDT
This bug has been copied from bug #517329 and has been proposed to be backported to 4.8 z-stream (EUS).
Comment 3 Vitaly Mayatskikh 2009-10-02 06:48:40 EDT
Committed in 89.0.13
Comment 7 errata-xmlrpc 2009-10-22 11:09:51 EDT
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1522.html
Comment 8 Douglas Silas 2011-01-30 19:03:21 EST
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: The data buffer ethtool_get_strings() allocated, for the igb driver, was smaller than the amount of data that was copied in igb_get_strings(), because of a miscalculation in IGB_QUEUE_STATS_LEN, resulting in memory corruption. This bug could have led to a kernel panic.