Bug 214288 - CVE-2006-5757 ISO9660 __find_get_block_slow() denial of service
CVE-2006-5757 ISO9660 __find_get_block_slow() denial of service
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Eric Sandeen
Brian Brock
: Security
Depends On:
Blocks: 214419
  Show dependency treegraph
Reported: 2006-11-06 17:06 EST by Marcel Holtmann
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2007-0014
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-30 09:41:48 EST
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 Marcel Holtmann 2006-11-06 17:06:53 EST
Reported as MOKB-05-11-2006:


The ISO9660 filesystem handling code of the Linux 2.6.x kernel fails to properly
handle corrupted data structures, leading to an exploitable denial of service
condition. This particular vulnerability seems to be caused by a race condition
and a signedness issue. When performing a read operation on a corrupted ISO9660
fs stream, the isofs_get_blocks() function will enter an infinite loop when
__find_get_block_slow() callback from sb_getblk() fails ("due to various races
between file io on the block device and getblk").
Comment 5 Jason Baron 2006-11-10 16:59:16 EST
committed in stream U5 build 42.24. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 7 Mike Gahagan 2007-01-18 13:07:24 EST
verified with the mokb image and numerous runs of fsfuzz have not reproduced
similar behavior.

Comment 9 Red Hat Bugzilla 2007-01-30 09:41:48 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.