linux-kernel - Re: [PATCH 1/2] prctl: more prctl(PR_SET_MM

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: <20150527221214.GA27996@p183.telecom.by>
Date:	Thu, 28 May 2015 01:12:14 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	jarod@...hat.com, jstancek@...hat.com
Subject: Re: [PATCH 1/2] prctl: more prctl(PR_SET_MM_*) checks

On Thu, May 28, 2015 at 01:02:29AM +0300, Cyrill Gorcunov wrote:
> On Thu, May 28, 2015 at 12:47:57AM +0300, Alexey Dobriyan wrote:
> > Individual prctl(PR_SET_MM_*) calls do some checking to maintain
> > consistent view of mm->arg_start et al fields, but not enough.
> > In particular PR_SET_MM_ARG_START/PR_SET_MM_ARG_END/PR_SET_MM_ENV_START/PR_SET_MM_ENV_END
> > only check that address lies in existent VMA, but doesn't check that
> > start address is lower that end address _at all_.
> > 
> > Consolidate all consistency checks, so there will be no difference in
> > the future between PR_SET_MM_MAP and individual PR_SET_MM_* calls.
> > 
> > The program below makes both ARGV and ENVP areas reverted,
> > makes /proc/$PID/cmdline show garbage (doesn't oops by luck).
> 
> Why should it oops?

Anything can happen if you constantly write code like this

	unsigned long len = mm->arg_end - mm->arg_start;

and expect result to be positive.
--
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/