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:
Willy Tarreau <w@1wt.eu> [@nathanchance: fixed conflict related to 2995d726] Signed-off-by:
Nathan Chancellor <natechancellor@gmail.com>
Loading
Please register or sign in to comment