[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090728011943.589176cb@lxorguk.ukuu.org.uk>
Date: Tue, 28 Jul 2009 01:19:43 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: James Morris <jmorris@...ei.org>
Cc: James Carter <jwcart2@...ho.nsa.gov>,
Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, selinux@...ho.nsa.gov,
Stephen Smalley <sds@...ho.nsa.gov>, spender@...ecurity.net,
Daniel J Walsh <dwalsh@...hat.com>, cl@...ux-foundation.org,
Arjan van de Ven <arjan@...radead.org>, kees@...flux.net,
Chad Sellers <csellers@...sys.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
mingo@...e.hu
Subject: Re: mmap_min_addr and your local LSM (ok, just SELinux)
A dumb question perhaps, but while addling my brain over the tty layer I
was wondering if for the specific case of jump through NULL (which seems
to be the most common but by no means only problem case that gets
exploited) is there any reason we can't set a default breakpoint for
executing 0 and fix that up as a trap in the kernel ?
Even user code that needs zero page mapped such as BIOS hackery doesn't
actually jump through zero often if ever, and would be a userspace not a
kernel space trap source so could be fixed up.
Just a random "I've been staring at code too long today" thought ?
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/
Powered by blists - more mailing lists