This patch contains SD40 Wi-Fi driver (v22.3.5.16) for Medea and fixes WPA2 KRACK vulnerability.
The following issues have been resolved in this release:
▪ KRACK vulnerability – Fixed WPA2 KRACK vulnerability (12108, 12159)
▪ Managed LCM stability updates – Fixed several stability issues. (11981, 12188)
▪ Managed LCM WEP key limited – Fixed an issue that limited the character set available when configuring a passphrase-based WEP key. (11996)
▪ WEC2013 Information Broker load failure – Fixed an issue that prevented the Information Broker debug engine from loading correctly in WEC2013. (11976)
▪ Driver crash at suspend – Fixed an issue that could cause the driver to crash at suspend, leading to a reboot on some platforms. (12130)
The following issues have been resolved in this release:
▪ Radio hang at low RSSI – Fixed an issue that could cause the radio to hang while continuously transmitting data at very low RSSI. (11684)
▪ Certificate load failure – Fixed an issue that prevented the supplicant from finding a certificate in the store until a reboot occurred if the certificate was loaded while the supplicant was running. (11037)
▪ LCM stability updates – Fixed several stability issues in the LCM profiles dialog. (10576, 11435, 11529)
▪ Supplicant upgraded– The Laird supplicant has been rebased to WPA supplicant v2.6
▪ Buffer overflow with potential data corruption – Fixed several issues with the Laird Bluetooth stack implementation that caused buffer overflows and potential data corruption. (10760)
▪ Radio modes not displayed correctly – Fixed an issue in SCU that caused the available radio modes to be displayed incorrectly in some cases. (7770, 9436)
▪ LCM/SCU user interface issues – Fixed several user interface issues in SCU and LCM. (8239, 8563)
▪ Bluetooth initialization procedure improved – Modified the Bluetooth initialization procedure to unconditionally occur at device boot, instead of waiting on the Bluetooth stack to be enabled. By default, the radio is not re-initialized at resume. However, if the radio is reset or powered down during suspend the initialization procedure needs to occur again. (10433) This can be enabled by setting the following registry key: [HKEY_LOCAL_MACHINESoftwareSummitBT] registry key: PatchOnResume = 1
▪ Bluetooth initialization performance – Significant improvement in the Bluetooth radio initialization and patching process. (9710)
▪ Edge of coverage robustness – Improved connection robustness in edge of coverage scenarios in heavily saturated RF environments. (9483, 10656, 10657)
▪ WEP key incorrectly masked when creating profile – Fixed an issue that caused the WEP key to be masked when entered during profile creation from the scan dialog. (10556)
▪ Edge of coverage robustness – Improved connection robustness in edge of coverage scenarios. (9483, 9751, 10277, 10305)
▪ Multiple ssids mapped to the same BSSID – Fixed a connection issue that can occur when a controller based infrastructure re-uses the same BSSID with different SSIDs on different bands. (10261)
▪ Unable to connect using WZC in a high AP environment – Fixed several issues that could prevent connecting using the Microsoft supplicant/WZC in a high AP environment. (5726, 10263, 10269)
▪ Hang after authentication response failure – Fixed an issue that caused a driver hang to occur if an 802.11 authentication failure response was received. (10426)
▪ EAP-TLS fails if TLSv1.2 is used – Fixed an issue that caused authentication to fail if TLS version 1.2 is used. This issue only occurred if the authentication server supported TLSv1.2. (9262, 10372)
▪ Connection drop when broadcast key rotation packet received – Fixed an issue that caused the connection to drop if the AP transmitted an incorrectly formatted broadcast key rotation packet. (9475)
▪ EAP-TTLS with inner method CHAP/MSCHAP fails with TLS version 1.2 – Worked around an issue on some versions of the FreeRadius authentication server that caused authentication to fail when using EAP-TTLS with inner method CHAP/MSCHAP and TLSv1.2. (9554)
▪ TLS middle certificate validation fails – Fixed an issue that caused TLS middle certificate validation to fail in some cases. (9598)
▪ Asterisks not allowed in PSK passphrase – Fixed an issue that prevented asterisks from being used in a PSK passphrase in the LCM. (9713)
▪ Profile changes not always persisted across a reboot – Fixed an issue that sometimes caused profile changes to be lost if a registry flush did not occur prior to a device reboot. (8278)
▪ GetWEPKey does not indicate txKey – Fixed an issue that prevented the GetWEPKey() API from returning the correct transmit key. (9764)
▪ UNII-2E support in Korea – Added support for UNII-2E channels in Korea. (9577, 9578)
▪ Short Guard Interval forced on – Fixed an issue that caused Short Guard Interval to be used unconditionally when connecting to HT capable access points. This caused various communications failures when connected to older access points that did not support SGI. (9479, 9536)
▪ Singapore channel support – Added support for channels 100-140 in Singapore. (7981)
▪ Australia and New Zealand channel support – Fixed an issue that prevented channels 12 and 13 from being available in Australia and New Zealand. (8894)
▪ Regulatory domain reported incorrectly – Fixed an issue that could cause the regulatory domain to be incorrectly reported as FCC if the device was configured for WW regulatory domain and no country code had been received. (8946)
▪ Incorrect country code adoption – Fixed an issue that prevented the device from adopting the best country code candidate when the connected AP was not broadcasting the same country code as the majority of surrounding APs. (9089)
▪ Driver hang – Fixed an issue that sometimes caused the driver to stop responding if a scan occurred during a period of high data transfer. (9131)
▪ Failure to connect in A Only mode – Fixed an issue that prevented the radio from connecting in some regulatory domains if configured for A Rates Only. (9162)
▪ Unable to connect after adapter disable/enable – Fixed an issue that prevented the radio from connecting after the network adapter was disabled and re-enabled. This issue could appear on some operating systems when using ActiveSync configured to block the data connection. (8564)
▪ Connect failure using autoprofile – Fixed an issue that sometimes prevented the radio from connecting after a profile change triggered by autoprofile logic. (8590)
▪ Connect failure after interrupted scan – Fixed an issue that prevented the radio from connecting if it was interrupted with a profile change or disassociate request while scanning. (8609, 8748)
▪ Connect failure after disconnect in third party mode – Fixed an issue that prevented the radio from connecting after a disconnect event when using the Microsoft supplicant. (8746)
▪ Managed SDK Import/Export failure – Fixed an issue with the import/export logic in the managed SDK library. (8599, 8600)