Linux MM tree latest commits
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: deller@gmx.de, ilja@netric.org, kyle@mcmartin.ca, stable@kernel.org
Subject: + parisc-ledc-fix-potential-stack-overflow-in-led_proc_write.patch added to -mm tree
Date: Tue, 03 Aug 2010 15:40:02 -0700	[thread overview]
Message-ID: <201008032240.o73Me2Hr015284@imap1.linux-foundation.org> (raw)


The patch titled
     parisc: led.c: fix potential stack overflow in led_proc_write()
has been added to the -mm tree.  Its filename is
     parisc-ledc-fix-potential-stack-overflow-in-led_proc_write.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: parisc: led.c: fix potential stack overflow in led_proc_write()
From: Helge Deller <deller@gmx.de>

Avoid potential stack overflow by correctly checking count parameter.

Signed-off-by: Helge Deller <deller@gmx.de>
Reported-by: Ilja <ilja@netric.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 drivers/parisc/led.c |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff -puN drivers/parisc/led.c~parisc-ledc-fix-potential-stack-overflow-in-led_proc_write drivers/parisc/led.c
--- a/drivers/parisc/led.c~parisc-ledc-fix-potential-stack-overflow-in-led_proc_write
+++ a/drivers/parisc/led.c
@@ -176,16 +176,18 @@ static ssize_t led_proc_write(struct fil
 	size_t count, loff_t *pos)
 {
 	void *data = PDE(file->f_path.dentry->d_inode)->data;
-	char *cur, lbuf[count + 1];
+	char *cur, lbuf[32];
 	int d;
 
 	if (!capable(CAP_SYS_ADMIN))
 		return -EACCES;
 
-	memset(lbuf, 0, count + 1);
+	if (count >= sizeof(lbuf))
+		count = sizeof(lbuf)-1;
 
 	if (copy_from_user(lbuf, buf, count))
 		return -EFAULT;
+	lbuf[count] = 0;
 
 	cur = lbuf;
 
_

Patches currently in -mm which might be from deller@gmx.de are

parisc-fix-wrong-page-aligned-size-calculation-in-ioremapping-code.patch
kmap_atomic-make-kunmap_atomic-harder-to-misuse.patch
parisc-ledc-fix-potential-stack-overflow-in-led_proc_write.patch
dma-mapping-parisc-set-arch_dma_minalign.patch


                 reply	other threads:[~2010-08-03 22:40 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=201008032240.o73Me2Hr015284@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=deller@gmx.de \
    --cc=ilja@netric.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=stable@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