From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Luciano Coelho <coelho@ti.com>, Arik Nemtsov <arik@wizery.com>,
linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: check if key has TKIP type before updating IV
Date: Tue, 09 Oct 2012 20:50:12 +0200 [thread overview]
Message-ID: <1349808612.4683.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20121002193422.GA12214@redhat.com>
On Tue, 2012-10-02 at 21:34 +0200, Stanislaw Gruszka wrote:
> This patch fix corruption which can manifest itself by following crash
> when switching on rfkill switch with rt2x00 driver:
> https://bugzilla.redhat.com/attachment.cgi?id=615362
>
> Pointer key->u.ccmp.tfm of group key get corrupted in:
>
> ieee80211_rx_h_michael_mic_verify():
>
> /* update IV in key information to be able to detect replays */
> rx->key->u.tkip.rx[rx->security_idx].iv32 = rx->tkip_iv32;
> rx->key->u.tkip.rx[rx->security_idx].iv16 = rx->tkip_iv16;
>
> because rt2x00 always set RX_FLAG_MMIC_STRIPPED, even if key is not TKIP.
>
> We already check type of the key in different path in
> ieee80211_rx_h_michael_mic_verify() function, so adding additional
> check here is reasonable.
>
> Cc: stable@vger.kernel.org # 3.0+
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Looks fine, John, could you also pick this up for 3.7?
johannes
prev parent reply other threads:[~2012-10-09 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 19:34 [PATCH] mac80211: check if key has TKIP type before updating IV Stanislaw Gruszka
2012-10-09 18:50 ` Johannes Berg [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=1349808612.4683.21.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--cc=chunkeey@googlemail.com \
--cc=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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;
as well as URLs for NNTP newsgroup(s).