linux-kernel - Re: NULL pointer dereference in sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061022181102.GC27152@redhat.com>
Date:	Sun, 22 Oct 2006 14:11:02 -0400
From:	Dave Jones <davej@...hat.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Michael Buesch <mb@...sch.de>, Greg KH <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: NULL pointer dereference in sysfs_readdir

On Sun, Oct 22, 2006 at 11:08:58AM +0200, Stefan Richter wrote:

 > What if "next" became NULL afterwards? I know it's unlikely (but so is
 > the whole bug, given that we have just one reporter despite the bug's
 > age), but is it impossible? IOW does sysfs_readdir have any indirect
 > mutex protection?
 > 
 > Dave, do you patch sysfs datatypes in FC's kernel, or types they include?

Not that I recall. <linux/sysfs.h> is untouched in the trees I just
looked at (only have .18 ones handy right now)

	Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/