linux-kernel - Re: [patch] remove MNT_NOEXEC check for PROT

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: <200609242206.20446.vda.linux@googlemail.com>
Date:	Sun, 24 Sep 2006 22:06:20 +0200
From:	Denis Vlasenko <vda.linux@...glemail.com>
To:	Stas Sergeev <stsp@...et.ru>
Cc:	Ulrich Drepper <drepper@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Hugh Dickins <hugh@...itas.com>, Andrew Morton <akpm@...l.org>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] remove MNT_NOEXEC check for PROT_EXEC mmaps

On Sunday 24 September 2006 20:09, Stas Sergeev wrote:
> Ulrich Drepper wrote:
> > The consensus has been to add the same checks to mprotect.  They were
> > not left out intentionally.
> But how about the anonymous mmap with PROT_EXEC set?
> This is exactly what the malicious loader will do, it

If attacker has malicious loaders on the system,
the situation is already sort of hopeless.

Stas, I think noexec mounts are meant to prevent
_accidental_ execution of binaries/libs from that
filesystem. Think VFAT partition here, where all
files have execute bits set.

If user wants to execute binary blob from that fs
bad enough, he will do it. Maybe just by
copying file first to /tmp.

> won't do the shared (or private) file-backed mmap.
> So your technique doesn't restrict the malicious
> loaders, including the potential script loader you
> were referring to. It doesn't even make their life
> any harder. Only the properly-written programs suffer.
> Or, in case of ceasing to use noexec - the security.
--
vda
-
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/