Ajith C <quic_ajithc@xxxxxxxxxxx> wrote: > Currently, if the access point receives an association > request containing an Extended HE Capabilities Information > Element with an invalid MCS-NSS, it triggers a firmware > crash. > > This issue arises when EHT-PHY capabilities shows support > for a bandwidth and MCS-NSS set for that particular > bandwidth is filled by zeros and due to this, driver obtains > peer_nss as 0 and sending this value to firmware causes > crash. > > Address this issue by implementing a validation step for > the peer_nss value before passing it to the firmware. If > the value is greater than zero, proceed with forwarding > it to the firmware. However, if the value is invalid, > reject the association request to prevent potential > firmware crashes. > > Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1 > > Signed-off-by: Ajith C <quic_ajithc@xxxxxxxxxxx> > Acked-by: Jeff Johnson <quic_jjohnson@xxxxxxxxxxx> > Signed-off-by: Kalle Valo <quic_kvalo@xxxxxxxxxxx> Patch applied to ath-next branch of ath.git, thanks. db163a463bb9 wifi: ath12k: fix firmware crash due to invalid peer nss -- https://patchwork.kernel.org/project/linux-wireless/patch/20240613053528.2541645-1-quic_ajithc@xxxxxxxxxxx/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
