netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: drosenberg@vsecurity.com
Cc: samuel@sortiz.org, netdev@vger.kernel.org, security@kernel.org
Subject: Re: [PATCH v2] irda: prevent heap corruption on invalid nickname
Date: Sun, 27 Mar 2011 17:59:14 -0700 (PDT)	[thread overview]
Message-ID: <20110327.175914.71098822.davem@davemloft.net> (raw)
In-Reply-To: <1300601670.1869.5.camel@dan>

From: Dan Rosenberg <drosenberg@vsecurity.com>
Date: Sun, 20 Mar 2011 02:14:30 -0400

> Invalid nicknames containing only spaces will result in an underflow in
> a memcpy size calculation, subsequently destroying the heap and
> panicking.
> 
> v2 also catches the case where the provided nickname is longer than the
> buffer size, which can result in controllable heap corruption.
> 
> Signed-off-by: Dan Rosenberg <drosenberg@vsecurity.com>
> Cc: stable@kernel.org

Applied.

      reply	other threads:[~2011-03-28  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20  6:14 [PATCH v2] irda: prevent heap corruption on invalid nickname Dan Rosenberg
2011-03-28  0:59 ` David Miller [this message]

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=20110327.175914.71098822.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=drosenberg@vsecurity.com \
    --cc=netdev@vger.kernel.org \
    --cc=samuel@sortiz.org \
    --cc=security@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).