diff options
| author | Brian Norris <briannorris@chromium.org> | 2017-07-25 04:13:19 +0300 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2017-07-28 17:47:46 +0300 |
| commit | 7dc4a6b5ca942a7196e17ecb3827b406cf79bc60 (patch) | |
| tree | bfc5a82e503246bf1967b3a979325f3a166d94c5 /include | |
| parent | 4b1f5a0d2eeb988d3e77dce7210e3ad3136b0912 (diff) | |
| download | linux-7dc4a6b5ca942a7196e17ecb3827b406cf79bc60.tar.xz | |
mwifiex: pcie: don't allow cmd buffer reuse after reset
In rogue cases (due to other bugs) it's possible we try to process an
old command response *after* resetting the device. This could trigger a
double-free (or the SKB can get reallocated elsewhere...causing other
memory corruptions) in mwifiex_pcie_process_cmd_complete().
For safety (and symmetry) let's always NULL out the command buffer as we
free it up. We're already doing this for the command response buffer.
Signed-off-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions
