From: Daniel Mack <daniel@caiaq.de>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Holger Schurig <holgerschurig@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Maithili Hinge <maithili@marvell.com>,
Kiran Divekar <dkiran@marvell.com>,
Michael Hirsch <m.hirsch@raumfeld.com>,
netdev@vger.kernel.org, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] Libertas: fix buffer overflow in lbs_get_essid()
Date: Thu, 17 Dec 2009 07:15:08 +0800 [thread overview]
Message-ID: <20091216231508.GX28375@buzzloop.caiaq.de> (raw)
In-Reply-To: <1260982667.2179.9.camel@localhost.localdomain>
On Wed, Dec 16, 2009 at 08:57:47AM -0800, Dan Williams wrote:
> On Wed, 2009-12-16 at 05:12 +0100, Daniel Mack wrote:
> > The libertas driver copies the SSID buffer back to the wireless core and
> > appends a trailing NULL character for termination. This is
> >
> > a) unnecessary because the buffer is allocated with kzalloc and is hence
> > already NULLed when this function is called, and
> >
> > b) for priv->curbssparams.ssid_len == 32, it writes back one byte too
> > much which causes memory corruptions.
> >
> > Fix this by removing the extra write.
>
> Acked-by: Dan Williams <dcbw@redhat.com>
Thanks, everyone. Who will care to pick an queue this one?
Daniel
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Dan Williams <dcbw@redhat.com>
> > Cc: Holger Schurig <holgerschurig@gmail.com>
> > Cc: John W. Linville <linville@tuxdriver.com>
> > Cc: Stephen Hemminger <shemminger@vyatta.com>
> > Cc: Maithili Hinge <maithili@marvell.com>
> > Cc: Kiran Divekar <dkiran@marvell.com>
> > Cc: Michael Hirsch <m.hirsch@raumfeld.com>
> > Cc: netdev@vger.kernel.org
> > Cc: libertas-dev@lists.infradead.org
> > Cc: linux-wireless@lists.infradead.org
> > Cc: stable@kernel.org
> > ---
> > drivers/net/wireless/libertas/wext.c | 2 --
> > 1 files changed, 0 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/wireless/libertas/wext.c b/drivers/net/wireless/libertas/wext.c
> > index be837a0..01c738b 100644
> > --- a/drivers/net/wireless/libertas/wext.c
> > +++ b/drivers/net/wireless/libertas/wext.c
> > @@ -1953,10 +1953,8 @@ static int lbs_get_essid(struct net_device *dev, struct iw_request_info *info,
> > if (priv->connect_status == LBS_CONNECTED) {
> > memcpy(extra, priv->curbssparams.ssid,
> > priv->curbssparams.ssid_len);
> > - extra[priv->curbssparams.ssid_len] = '\0';
> > } else {
> > memset(extra, 0, 32);
> > - extra[priv->curbssparams.ssid_len] = '\0';
> > }
> > /*
> > * If none, we may want to get the one that was set
>
next prev parent reply other threads:[~2009-12-16 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 4:12 [PATCH] Libertas: fix buffer overflow in lbs_get_essid() Daniel Mack
2009-12-16 4:18 ` Daniel Mack
2009-12-16 8:15 ` Holger Schurig
2009-12-16 16:57 ` Dan Williams
2009-12-16 23:15 ` Daniel Mack [this message]
2009-12-17 1:01 ` John W. Linville
2009-12-17 1:19 ` Dan Williams
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=20091216231508.GX28375@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=dcbw@redhat.com \
--cc=dkiran@marvell.com \
--cc=holgerschurig@gmail.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.hirsch@raumfeld.com \
--cc=maithili@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--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;
as well as URLs for NNTP newsgroup(s).