linux-kernel - Re: Registration Weakness in Linux Kernel's Binary formats

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: <1159916054.17553.92.camel@localhost.localdomain>
Date:	Tue, 03 Oct 2006 23:54:14 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Chase Venters <chase.venters@...entec.com>
Cc:	SHELLCODE Security Research <GoodFellas@...llcode.com.ar>,
	linux-kernel@...r.kernel.org
Subject: Re: Registration Weakness in Linux Kernel's Binary formats

Ar Maw, 2006-10-03 am 16:48 -0500, ysgrifennodd Chase Venters:
> So the problem you find is that newly registered binfmts are inserted into 
> the front of the binfmt list instead of the rear, and this means that a 
> binfmt handler can slip in at runtime at run quietly before any other 
> handler?

This is a feature as anyone trying to debug versions of the elf loader
could would find out quite fast.

> 
> I'm not sure I see this as a real problem. If you can load a module into 
> kernel space and access arbitrary symbols (not to mention run in ring 0) I 
> think you can do a lot more than just hide out on the binfmt list.
> 
> Am I missing something?

Don't think so. At the point you can load code into the kernel you can
replace any code anyway.

NOTABUG

Alan

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