Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 167696 - CVE-2005-2800 SCSI proc DoS
CVE-2005-2800 SCSI proc DoS
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Doug Ledford
Brian Brock
: Security
Depends On:
Blocks: 168429
  Show dependency treegraph
Reported: 2005-09-07 06:09 EDT by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2006-0101
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-17 03:32:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:808 normal SHIPPED_LIVE Important: kernel security update 2005-10-27 00:00:00 EDT
Red Hat Product Errata RHSA-2006:0101 normal SHIPPED_LIVE Important: kernel security update 2006-01-17 00:00:00 EST

  None (edit)
Description Mark J. Cox 2005-09-07 06:09:46 EDT
"Memory leak in the seq_file implemenetation in the SCSI procfs interface (sg.c)
in Linux kernel 2.6.13 and earlier allows local users to cause a denial of
service (memory consumption) via certain repeated reads from the
/proc/scsi/sg/devices file, which is not properly handled when the next()
iterator returns NULL or an error."

Affects: RHEL4

Fix: Upstream at
Comment 1 Doug Ledford 2005-10-18 13:28:32 EDT
Fix is being tested now.
Comment 2 Doug Ledford 2005-10-18 19:18:15 EDT
Fix passed my testing, submitted internally for inclusion.
Comment 7 Red Hat Bugzilla 2006-01-17 03:32:45 EST
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.


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