This is a note to let you know that I've just added the patch titled
mac80211: fix potential use-after-free
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mac80211-fix-potential-use-after-free.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From d2722f8b87fb172ff2f31d3a2816b31d58678d40 Mon Sep 17 00:00:00 2001
From: Johannes Berg <[email protected]>
Date: Tue, 4 Mar 2014 11:43:28 +0100
Subject: mac80211: fix potential use-after-free
From: Johannes Berg <[email protected]>
commit d2722f8b87fb172ff2f31d3a2816b31d58678d40 upstream.
The bss struct might be freed in ieee80211_rx_bss_put(),
so we shouldn't use it afterwards.
Fixes: 817cee7675237 ("mac80211: track AP's beacon rate and give it to the
driver")
Signed-off-by: Johannes Berg <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
net/mac80211/mlme.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -2708,8 +2708,8 @@ static void ieee80211_rx_bss_info(struct
bss = ieee80211_bss_info_update(local, rx_status, mgmt, len, elems,
channel);
if (bss) {
- ieee80211_rx_bss_put(local, bss);
sdata->vif.bss_conf.beacon_rate = bss->beacon_rate;
+ ieee80211_rx_bss_put(local, bss);
}
}
Patches currently in stable-queue which might be from [email protected]
are
queue-3.14/mac80211-fix-software-remain-on-channel-implementation.patch
queue-3.14/mac80211-fix-suspend-vs.-authentication-race.patch
queue-3.14/mac80211-exclude-ap_vlan-interfaces-from-tx-power-calculation.patch
queue-3.14/mac80211-fix-wpa-with-vlan-on-ap-side-with-ps-sta-again.patch
queue-3.14/mac80211-fix-potential-use-after-free.patch
queue-3.14/iwlwifi-dvm-take-mutex-when-sending-sync-bt-config-command.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
