linux-kernel - Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs

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: <Pine.LNX.4.64.0609061120430.27779@g5.osdl.org>
Date:	Wed, 6 Sep 2006 11:24:05 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Kirill Korotaev <dev@...nvz.org>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Fernando Vazquez <fernando@....ntt.co.jp>,
	"David S. Miller" <davem@...emloft.net>, tony.luck@...el.com,
	linux-ia64@...r.kernel.org, stable@...nel.org, xemul@...nvz.org,
	devel@...nvz.org
Subject: Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs

On Mon, 4 Sep 2006, Kirill Korotaev wrote:
> 
> this patch is already commited into -stable 2.6.17.y tree.

I don't like it. Apparently the patch was bad, and broken on MIPS and 
parisc, and it was applied to the stable tree without being in the 
standard tree.

If MIPS and parisc don't matter for the stable tree (very possible - there 
are no big commercial distributions for them), then dammit, neither should 
ia64 and sparc (there are no big commercial distros for them either). 
Either way, it seems this didn't happen the way it should have.

The proper fix would _seem_ to have the whole

	#ifndef arch_mmap_check
	#define arch_mmap_check(addr, len, flags) (0)
	#endif

in the only file that actually _uses_ this, namely mm/mmap.c. Rather than 
pollute lots of architecture-specific files with this macro that nobody 
really is interested in except for ia64 and sparc.

			Linus
-
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/