summaryrefslogtreecommitdiff
path: root/arch/s390
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2014-02-01 00:16:23 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-02-22 10:32:45 -0800
commitfb11ab59b2999e2afee7c7fcd3687bf07b2fc988 (patch)
tree45835c3a6f71d27876e248647723790aec483dd9 /arch/s390
parentce5562e5704bf715fc3084d9f218e5ba3fbf0991 (diff)
downloadlwn-fb11ab59b2999e2afee7c7fcd3687bf07b2fc988.tar.gz
lwn-fb11ab59b2999e2afee7c7fcd3687bf07b2fc988.zip
mac80211: fix fragmentation code, particularly for encryption
commit 338f977f4eb441e69bb9a46eaa0ac715c931a67f upstream. The "new" fragmentation code (since my rewrite almost 5 years ago) erroneously sets skb->len rather than using skb_trim() to adjust the length of the first fragment after copying out all the others. This leaves the skb tail pointer pointing to after where the data originally ended, and thus causes the encryption MIC to be written at that point, rather than where it belongs: immediately after the data. The impact of this is that if software encryption is done, then a) encryption doesn't work for the first fragment, the connection becomes unusable as the first fragment will never be properly verified at the receiver, the MIC is practically guaranteed to be wrong b) we leak up to 8 bytes of plaintext (!) of the packet out into the air This is only mitigated by the fact that many devices are capable of doing encryption in hardware, in which case this can't happen as the tail pointer is irrelevant in that case. Additionally, fragmentation is not used very frequently and would normally have to be configured manually. Fix this by using skb_trim() properly. Fixes: 2de8e0d999b8 ("mac80211: rewrite fragmentation") Reported-by: Jouni Malinen <j@w1.fi> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions