Bug 125170 - CAN-2004-0535 e100e1000 kernel memory leak (x86)
CAN-2004-0535 e100e1000 kernel memory leak (x86)
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
: Security
Depends On:
  Show dependency treegraph
Reported: 2004-06-03 08:40 EDT by Mark J. Cox (Product Security)
Modified: 2013-07-02 22:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-03 17:48:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2004-06-03 08:40:26 EDT
According to
http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.27.log a
recent kernel fix was applied "e1000: fix probable security hole".

This issue in fact is a minor information leak via the e1000 driver
that can reveal 24 bytes of kernel memory to users (if e1000 driver is

RHEL 2.1 is possibly vulnerable to this issue via the backported
driver added

No CVE name yet available
See Bug #125168 for a patch (will need to be backported)
Comment 1 Mark J. Cox (Product Security) 2004-06-04 04:01:07 EDT
Comment 4 John W. Linville 2004-07-30 16:17:04 EDT
This is covered by e1000 update in RHEL2.1 U5...
Comment 5 Mark J. Cox (Product Security) 2004-07-31 13:33:41 EDT
Reopening, needs to stay open until the release is actually shipped.
Comment 6 Mark J. Cox (Product Security) 2004-08-03 17:48:14 EDT
An errata 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.


Note You need to log in before you can comment on or make changes to this bug.