[PATCH] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

2016-09-15 Thread Arend van Spriel
commit ded89912156b1a47d940a0c954c43afbabd0c42c upstream User-space can choose to omit NL80211_ATTR_SSID and only provide raw IE TLV data. When doing so it can provide SSID IE with length exceeding the allowed size. The driver further processes this IE copying it into a local variable without

[PATCH] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

2016-09-15 Thread Arend van Spriel
commit ded89912156b1a47d940a0c954c43afbabd0c42c upstream User-space can choose to omit NL80211_ATTR_SSID and only provide raw IE TLV data. When doing so it can provide SSID IE with length exceeding the allowed size. The driver further processes this IE copying it into a local variable without

Re: [PATCH] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

2016-09-05 Thread Arend Van Spriel
On 5-9-2016 11:45, Arend van Spriel wrote: > User-space can choose to omit NL80211_ATTR_SSID and only provide raw > IE TLV data. When doing so it can provide SSID IE with length exceeding > the allowed size. The driver further processes this IE copying it > into a local variable without checking

[PATCH] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap()

2016-09-05 Thread Arend van Spriel
User-space can choose to omit NL80211_ATTR_SSID and only provide raw IE TLV data. When doing so it can provide SSID IE with length exceeding the allowed size. The driver further processes this IE copying it into a local variable without checking the length. Hence stack can be corrupted and used as