summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2016-11-15 12:05:11 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-12-02 09:09:01 +0100
commit8316338a201b3cd57605fc6c4ea0d9ce8a0d35c0 (patch)
treebbdc298ad9448b14ff906c785a515ff3703201a1 /security
parent4df31626fc0804822cc967807fb8105d09e8ab38 (diff)
cfg80211: limit scan results cache size
commit 9853a55ef1bb66d7411136046060bbfb69c714fa upstream. It's possible to make scanning consume almost arbitrary amounts of memory, e.g. by sending beacon frames with random BSSIDs at high rates while somebody is scanning. Limit the number of BSS table entries we're willing to cache to 1000, limiting maximum memory usage to maybe 4-5MB, but lower in practice - that would be the case for having both full-sized beacon and probe response frames for each entry; this seems not possible in practice, so a limit of 1000 entries will likely be closer to 0.5 MB. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions