From: David Miller <davem@davemloft.net>
To: tomasw@gmail.com
Cc: johannes@sipsolutions.net, mcgrof@gmail.com,
linville@tuxdriver.com, yi.zhu@intel.com,
linux-wireless@vger.kernel.org, assaf.krauss@intel.com
Subject: Re: [RFC PATCH 1/2] mac80211: 11d Handling - Country Information Element
Date: Thu, 19 Jun 2008 15:04:48 -0700 (PDT) [thread overview]
Message-ID: <20080619.150448.24028711.davem@davemloft.net> (raw)
In-Reply-To: <1ba2fa240806191329w7aef4ccaq587915d41d999edd@mail.gmail.com>
From: "Tomas Winkler" <tomasw@gmail.com>
Date: Thu, 19 Jun 2008 23:29:55 +0300
> On Thu, Jun 19, 2008 at 11:18 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> >
> >> >> + if (country_ie_len < 6) {
> >> >> + printk(KERN_ERR "%s: country information element shorter (%d)"
> >> >> + " than expected.\n", __func__, country_ie_len);
> >> >
> >> > Remotely exploitable security bug.
> >
> >> Please explain,
> >
> > Sending broken frames will fill the disk.
>
> I see thanks (yeah, distors doesn't make separate log partitions as default)
How distros do their partitioning is neither here not there. And even
if they make a seperate log partition, that means it's still exploitable
in that you will no longer get the other non-spam log messages that might
be important to know about.
Any kernel log message triggerable remotely without any kind of rate
limiting is a bug.
next prev parent reply other threads:[~2008-06-19 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 18:35 [RFC PATCH 1/2] mac80211: 11d Handling - Country Information Element Tomas Winkler
2008-06-19 18:35 ` [RFC PATCH 2/2] mac80211: workaround for resetting the tx power Tomas Winkler
2008-06-19 19:04 ` Johannes Berg
2008-06-19 20:26 ` Tomas Winkler
2008-06-19 19:03 ` [RFC PATCH 1/2] mac80211: 11d Handling - Country Information Element Johannes Berg
2008-06-19 20:16 ` Tomas Winkler
2008-06-19 20:18 ` Johannes Berg
2008-06-19 20:29 ` Tomas Winkler
2008-06-19 22:04 ` David Miller [this message]
2008-06-19 22:32 ` Tomas Winkler
2008-07-23 13:15 ` Luis R. Rodriguez
2008-07-23 15:02 ` Tomas Winkler
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=20080619.150448.24028711.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=assaf.krauss@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.com \
/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