Bug 161789

Summary: GET_INDEX macro in aspm pci fixup code can overwrite end of the array
Product: Red Hat Enterprise Linux 4 Reporter: Neil Horman <nhorman>
Component: kernelAssignee: Neil Horman <nhorman>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: jbaron, poelstra, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2005-514 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 13:36:40 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:    
Bug Blocks: 156322    
Attachments:
Description Flags
Backport of Intels upstream patch to restrict the GET_INDEX array to only use the lower 3 bits of the devfn value none

Description Neil Horman 2005-06-27 11:57:15 UTC 
Description of problem:
the GET_INDEX macro in arch/i386/pci/fixup.c fails to only use the lower 3 bits
of a pci devices devfn value.  As such, certain pcidevices with a sufficiently
large bus/device/function tuple can index too far into the quirk_aspm_offset
array, overwriting parts of memory

Version-Release number of selected component (if applicable):
RHEL4, all versions

How reproducible:
Unknown

Steps to Reproduce:
1.
2.
3.
  
Actual results:
memory which is allocated immediately after the quirk_aspm_offset array can
become corrupted

Expected results:
No memory corruption

Additional info:
Comment 1 Neil Horman 2005-06-27 11:57:15 UTC 
Created attachment 116008 [details]
Backport of Intels upstream patch to restrict the GET_INDEX array to only use the lower 3 bits of the devfn value
Comment 7 Red Hat Bugzilla 2005-10-05 13:36:40 UTC 
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 the 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-2005-514.html