| 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
| ||
|
Message-ID: <48FF52F4.10702@redhat.com> Date: Wed, 22 Oct 2008 11:21:08 -0500 From: Eric Sandeen <sandeen@...hat.com> To: Greg KH <greg@...ah.com> CC: stable@...nel.org, ext4 development <linux-ext4@...r.kernel.org> Subject: Re: [stable] [PATCH] stable - ext[234]: Avoid printk floods in the face of directory corruption (CVE-2008-3528) Greg KH wrote: > On Wed, Oct 22, 2008 at 10:11:52AM -0500, Eric Sandeen wrote: >> This is a trivial backport of the following upstream commits: >> >> - bd39597cbd42a784105a04010100e27267481c67 (ext2) >> - cdbf6dba28e8e6268c8420857696309470009fd9 (ext3) >> - 9d9f177572d9e4eba0f2e18523b44f90dd51fe74 (ext4) >> >> This addresses CVE-2008-3528 >> >> ext[234]: Avoid printk floods in the face of directory corruption > > For what kernel releases is this applicable? .27? .26? .25? Earlier? Sorry.. it is applicable to pretty much any kernel in the past :) .27 certainly (that's what the patch is against), .26, .25.... yes. It's not a particularly dangerous condition - you have to somehow get the administrator to mount the filesystem before you can trigger the "exploit" (which is a DoS, essentially) - so, I don't know if it's worth porting back to the dawn of time... Thanks, -Eric > thanks, > > greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists