diff options
| author |   Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com> | 2025-05-16 16:02:07 +0530 |
|---|---|---|
| committer |   Johannes Berg <johannes.berg@intel.com> | 2025-05-21 09:26:28 +0200 |
| commit | 78a7a126dc5b8e3c5a3d4da9f513e0236d2dc1a3 (patch) | |
| tree | cd17e12af47651d81676d4eb3030387506945c92 /net/lapb/lapb_timer.c | |
| parent | wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() (diff) | |
| download | wireguard-linux-78a7a126dc5b8e3c5a3d4da9f513e0236d2dc1a3.tar.xz wireguard-linux-78a7a126dc5b8e3c5a3d4da9f513e0236d2dc1a3.zip | |
wifi: mac80211: validate SCAN_FLAG_AP in scan request during MLO
When an AP interface is already beaconing, a subsequent scan is not allowed
unless the user space explicitly sets the flag NL80211_SCAN_FLAG_AP in the
scan request. If this flag is not set, the scan request will be returned
with the error code -EOPNOTSUPP. However, this restriction currently
applies only to non-ML interfaces. For ML interfaces, scans are allowed
without this flag being explicitly set by the user space which is wrong.
This is because the beaconing check currently uses only the deflink, which
does not get set during MLO.
Hence to fix this, during MLO, use the existing helper
ieee80211_num_beaconing_links() to know if any of the link is beaconing.
Signed-off-by: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
Link: https://patch.msgid.link/20250516-bug_fix_mlo_scan-v2-1-12e59d9110ac@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions