From: Johannes Berg <johannes@sipsolutions.net>
To: Kees Cook <kees.cook@canonical.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Joe Perches <joe@perches.com>, Tejun Heo <tj@kernel.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [PATCH] wireless extensions: fix kernel heap content leak
Date: Mon, 30 Aug 2010 20:06:30 +0200 [thread overview]
Message-ID: <1283191590.3694.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100830180302.GM4703@outflux.net>
On Mon, 2010-08-30 at 11:03 -0700, Kees Cook wrote:
> Hi Johannes,
>
> On Mon, Aug 30, 2010 at 12:24:54PM +0200, Johannes Berg wrote:
> > --- wireless-testing.orig/net/wireless/wext-compat.c 2010-08-30 12:04:57.000000000 +0200
> > +++ wireless-testing/net/wireless/wext-compat.c 2010-08-30 12:11:32.000000000 +0200
> > @@ -1420,6 +1420,9 @@ int cfg80211_wext_giwessid(struct net_de
> > {
> > struct wireless_dev *wdev = dev->ieee80211_ptr;
> >
> > + data->flags = 0;
> > + data->length = 0;
> > +
> > switch (wdev->iftype) {
> > case NL80211_IFTYPE_ADHOC:
> > return cfg80211_ibss_wext_giwessid(dev, info, data, ssid);
>
> Thanks for all your work on this! Were you able to trigger the leak
> through cfg80211? If so, then this will need a CVE assigned and sent to
> stable too, I think.
Yes, I was, very easily, by doing an SIOCGIWESSID while unassociated,
with a large iwq->length set by userspace. I did CC stable on my patch,
but we can amend the commit by a CVE if so desired.
johannes
next prev parent reply other threads:[~2010-08-30 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 21:02 [PATCH] wireless: fix 64K kernel heap content leak via ioctl Kees Cook
2010-08-27 21:22 ` Jean Tourrilhes
2010-08-27 21:43 ` Kees Cook
[not found] ` <20100827214357.GE4703-oSa+0FWJbaXR7s880joybQ@public.gmane.org>
2010-08-27 21:53 ` Jean Tourrilhes
2010-08-27 22:35 ` Luis R. Rodriguez
[not found] ` <AANLkTimeEa_=dqX5yFnYzaSaL90TfOg3=MsydG81naAC-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-27 22:39 ` Jean Tourrilhes
2010-08-27 22:51 ` Luis R. Rodriguez
2010-08-30 8:47 ` Johannes Berg
2010-08-30 8:58 ` Johannes Berg
2010-08-30 9:59 ` Johannes Berg
2010-08-30 10:24 ` [PATCH] wireless extensions: fix kernel heap content leak Johannes Berg
[not found] ` <1283163894.3691.48.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-08-30 18:03 ` Kees Cook
2010-08-30 18:06 ` Johannes Berg [this message]
2010-08-30 17:40 ` [PATCH] wireless: fix 64K kernel heap content leak via ioctl Jean Tourrilhes
[not found] ` <20100830174018.GA3639-yAE0UhLNZJawPNPzzlOzwdBPR1lH4CV8@public.gmane.org>
2010-08-30 17:50 ` Johannes Berg
2010-09-15 22:48 ` [vendor-sec] " Greg KH
[not found] ` <20100915224836.GF19835-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2010-09-15 23:11 ` Johannes Berg
2010-09-15 23:28 ` Greg KH
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=1283191590.3694.7.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=jt@hpl.hp.com \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=tj@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).