Bug 152399 - CAN-2005-0400 ext2 mkdir() directory entry random kernel memory leak
Summary: CAN-2005-0400 ext2 mkdir() directory entry random kernel memory leak
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard: source=vendorsec,public=20050321,repo...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-29 09:59 UTC by Mark J. Cox
Modified: 2015-01-04 22:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-19 18:52:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:366 0 high SHIPPED_LIVE Important: kernel security update 2005-04-19 04:00:00 UTC

Description Mark J. Cox 2005-03-29 09:59:58 UTC
A flaw was discovered in ext2 filesystem support affecting 2.4 and 2.6 kernels.
 When a new directory is created, the ext2 block written to disk is initialized,
leading to an information leak.

The following script can easily show the problem on Linux 2.4 and 2.6:

#!/bin/sh
FILE=foo
dd if=/dev/zero of=$FILE bs=1k count=8192
mke2fs -F -b 1024 -m0 $FILE
mount -o loop $FILE mnt
for D in `seq 500` ; do mkdir mnt/$D ; done
umount mnt

Using 'strings foo' will reveal the information leak in the file.

Patch committed upstream, see

        fixed=2.6-bk (20050325
http://linux.bkbits.net:8080/linux-2.6/cset@4244bfc9vHVlT4nv2o4ys4_sf6vzKA
        fixed=2.4-bk (20050325 
http://linux.bkbits.net:8080/linux-2.4/cset@424473284plfEOB185qmyHPQyNPq4Q)

Comment 1 Mark J. Cox 2005-03-29 10:08:53 UTC
("is not initialized")

Comment 3 Josh Bressers 2005-04-19 18:52:27 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-366.html



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