mm-commits.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: drosenberg@vsecurity.com, alan@lxorguk.ukuu.org.uk,
	dan.j.rosenberg@gmail.com, greg@kroah.com
Subject: + drivers-char-nozomic-prevent-reading-uninitialized-stack-memory.patch added to -mm tree
Date: Thu, 16 Sep 2010 14:03:24 -0700	[thread overview]
Message-ID: <201009162103.o8GL3O8g013482@imap1.linux-foundation.org> (raw)


The patch titled
     drivers/char/nozomi.c: prevent reading uninitialized stack memory
has been added to the -mm tree.  Its filename is
     drivers-char-nozomic-prevent-reading-uninitialized-stack-memory.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: drivers/char/nozomi.c: prevent reading uninitialized stack memory
From: Dan Rosenberg <drosenberg@vsecurity.com>

The TIOCGICOUNT device ioctl allows unprivileged users to read
uninitialized stack memory, because the "reserved" member of the
serial_icounter_struct struct declared on the stack is not altered or
zeroed before being copied back to the user.  This patch takes care of it.

Signed-off-by: Dan Rosenberg <dan.j.rosenberg@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 drivers/char/nozomi.c |    2 ++
 1 file changed, 2 insertions(+)

diff -puN drivers/char/nozomi.c~drivers-char-nozomic-prevent-reading-uninitialized-stack-memory drivers/char/nozomi.c
--- a/drivers/char/nozomi.c~drivers-char-nozomic-prevent-reading-uninitialized-stack-memory
+++ a/drivers/char/nozomi.c
@@ -1809,6 +1809,8 @@ static int ntty_ioctl_tiocgicount(struct
 	const struct async_icount cnow = port->tty_icount;
 	struct serial_icounter_struct icount;
 
+	memset(&icount, 0, sizeof(struct serial_icounter_struct));
+
 	icount.cts = cnow.cts;
 	icount.dsr = cnow.dsr;
 	icount.rng = cnow.rng;
_

Patches currently in -mm which might be from drosenberg@vsecurity.com are

linux-next.patch
drivers-serial-serial_corec-prevent-reading-uninitialized-stack-memory.patch
drivers-char-amiserialc-prevent-reading-uninitialized-stack-memory.patch
drivers-char-nozomic-prevent-reading-uninitialized-stack-memory.patch


                 reply	other threads:[~2010-09-16 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201009162103.o8GL3O8g013482@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dan.j.rosenberg@gmail.com \
    --cc=drosenberg@vsecurity.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).