linux-kernel - Re: [RFC] perf: Prevent potential null dereference

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]

Date:	Mon, 6 Dec 2010 01:13:21 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC] perf: Prevent potential null dereference

On Thu, Dec 02, 2010 at 08:46:10PM -0200, Arnaldo Carvalho de Melo wrote:
> Em Thu, Dec 02, 2010 at 11:41:08PM +0100, Frederic Weisbecker escreveu:
> > On Fri, Dec 03, 2010 at 01:26:05AM +0300, Cyrill Gorcunov wrote:
> > > In case if there is no memory we might hit null
> > > dereference on accessing calloc'ed data.
> > > 
> > > Signed-off-by: Cyrill Gorcunov <gorcunov@...nvz.org>
> > > CC: Arnaldo Carvalho de Melo <acme@...hat.com>
> > > CC: Peter Zijlstra <peterz@...radead.org>
> > > CC: Ingo Molnar <mingo@...e.hu>
> > > CC: Frederic Weisbecker <fweisbec@...il.com>
> > > ---
...
> > 
> > Good.
> > 
> > As a nit, not that it matters that much because we are very close to the starting code
> > anyway, but it would be better to propagate the error to the callers.
> 
> I'm of the opinion that main() should be where exit() is allowed, and
> even there... return would be better. 8-)
> 
> - Arnaldo
> 

ok, sorry for delay, it seems the following would be liked
more than first version ;)

  Cyrill
---
[PATCH] perf: Prevent potential null dereference v2

In case if there is no memory we might hit null
dereference on accessing calloc'ed data.

v2: propagate error to a caller

Signed-off-by: Cyrill Gorcunov <gorcunov@...nvz.org>
CC: Arnaldo Carvalho de Melo <acme@...hat.com>,
CC: Peter Zijlstra <peterz@...radead.org>
CC: Ingo Molnar <mingo@...e.hu>
CC: Frederic Weisbecker <fweisbec@...il.com>
---

NB it's unclear for me why don't we yield any message on
too long command line, but anyway even then it should not
be messed with this particular patch.

Arnaldo, I'll check builtin-kmem.c next time i be able to,
though if there anyone would like to beat me on this -- feel
free ;)

 tools/perf/builtin-record.c |   14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

Index: linux-2.6.git/tools/perf/builtin-record.c
=====================================================================
--- linux-2.6.git.orig/tools/perf/builtin-record.c
+++ linux-2.6.git/tools/perf/builtin-record.c
@@ -507,7 +507,7 @@ static void mmap_read_all(void)
 		write_output(&finished_round_event, sizeof(finished_round_event));
 }
 
-static void comm__construct(int argc, const char **argv)
+static int comm__construct(int argc, const char **argv)
 {
 	char *comm, *tmp;
 	size_t size;
@@ -521,9 +521,13 @@ static void comm__construct(int argc, co
 	}
 
 	if ((long)size < 0)
-		return;
+		return 0;
 
 	comm = calloc(1, size);
+	if (!comm) {
+		pr_err("Not enough memory to construct internal command line.\n");
+		return -ENOMEM;
+	}
 
 	tmp = comm;
 	for (i = 0; i < argc; i++) {
@@ -533,6 +537,7 @@ static void comm__construct(int argc, co
 	}
 
 	session->command_line = comm;
+	return 0;
 }
 
 static int __cmd_record(int argc, const char **argv)
@@ -597,7 +602,10 @@ static int __cmd_record(int argc, const 
 	if (!no_buildid)
 		perf_header__set_feat(&session->header, HEADER_BUILD_ID);
 
-	comm__construct(argc, argv);
+	err = comm__construct(argc, argv);
+	if (err < 0)
+		goto out_delete_session;
+
 
 	if (!file_new) {
 		err = perf_header__read(session, output);
--
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/