ath5k: add bounds check to pdadc table
We check the bounds on pdadc once when correcting for negative curves but not when we later copy values from from the pdadc_tmp array, leading to a potential overrun. Although we shouldn't hit this case in practice, let's be consistent. Reported-by: Dan Carpenter <error27@gmail.com> Signed-off-by: Bob Copeland <me@bobcopeland.com> Acked-by: Bruno Randolf <br1@einfach.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
a05988bbbe
commit
4f59fce9e0
@ -2557,7 +2557,7 @@ ath5k_combine_pwr_to_pdadc_curves(struct ath5k_hw *ah,
|
||||
max_idx = (pdadc_n < table_size) ? pdadc_n : table_size;
|
||||
|
||||
/* Fill pdadc_out table */
|
||||
while (pdadc_0 < max_idx)
|
||||
while (pdadc_0 < max_idx && pdadc_i < 128)
|
||||
pdadc_out[pdadc_i++] = pdadc_tmp[pdadc_0++];
|
||||
|
||||
/* Need to extrapolate above this pdgain? */
|
||||
|
Loading…
Reference in New Issue
Block a user