wifi: mwifiex: fix permanently busy scans after multiple roam iterations

MITRE NVD CVE.ORG JSON API

Summary

CVECVE-2026-68469
StatePUBLISHED
AssignerLinux
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-08-15 06:19:57 UTC
Updated2026-08-15 06:19:57 UTC
DescriptionIn the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: fix permanently busy scans after multiple roam iterations In order for the firmware to sleep, the driver has to confirm a previously received sleep request. The normal sequence of evets goes like this: EVENT_SLEEP -> adapter->ps_state = PS_STATE_PRE_SLEEP -> sleep-confirm -> SLEEP -> EVENT_AWAKE -> AWAKE. Before sending the sleep-confirm command, the driver must make sure there are no commands either running or waiting to be completed. mwifiex_ret_802_11_associate() unconditionally sets ps_state = PS_STATE_AWAKE when it processes the association command response, outside of the normal powersave management flow. If EVENT_SLEEP arrives while the association command is in flight, ps_state is PRE_SLEEP when the association command response is parsed, and the forced AWAKE overwrites it. The deferred sleep-confirm is never sent. A subsequent scan_start command is correctly acknowledged, but the firmware doesn't generate scan_result events. The scan request never finishes, and additional requests from userspace fail with -EBUSY. After testing on both IW412 and W8997, I could only trigger the bug on the IW412 and observed the firmwares behave differently. On the IW412 the firmware still sends EVENT_SLEEP while the authentication / association process is ongoing. A W8997 under the same conditions seems to suppress power-save for the duration of the association, so PRE_SLEEP never coincided with the association response even after extended periods of testing using the loops described below (>12hours). On the IW412, the delay between commands that triggers an EVENT_SLEEP was empirically determined to be ~20ms. This delay can naturally occur when the driver is outputting debugging information (debug_mask = 0x00000037), in which situation the busy scans issue is repeatable while running "test 1)" as described below. If the delay between commands is less than ~20ms, the firmware stays awake and the issue was not reproducible running the same test. The host_mlme=false path also behaves differently. In this case, the entire authentication / association transaction is executed by one command (HostCmd_CMD_802_11_ASSOCIATE), and the firmware doesn't emit EVENT_SLEEP while the command is running. Remove the assignment so the ps_state is only manipulated in the paths that are related to powersave event handling and on the main workqueue for correct sleep confirmation. The following loop tests were performed (with debugging output enabled): 1) force roaming between two AP's, one 5GHz and one 2.4GHz, same SSID. Use wpa_cli to trigger the roaming behavior, sleep 2s between iterations. 2) force a disconnection to AP 1 and a connection to AP 2, test scan. Use wpa_cli to trigger the connection changes, sleep 2s between iterations. Each test ran in each device for at least 3 hours.

Risk And Classification

EPSS: 0.002120000 probability, percentile 0.117240000 (date 2026-08-15)

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e 2ed36b2586f16c480ed58de303af704c2235e16d git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e 5796eabe435d83544b6fe39851ce47ca68fdb778 git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e 31a2c409f8f58d20f0f6391c151421155768ed77 git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e deb5f0ae384f1cf41fccaf6375266db2f2911b2b git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e 1bc55db2d34756bd53e4460dbb699619ee13cd7f git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e a59cfa165aee3e29d06145041c0ebe46a51de604 git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e 6126e12bf8c87badeab41a164c9689ac88e5c160 git Not specified
CNA Linux Linux affected 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e d78a407bad6f500884a8606aea1a5a9207be4030 git Not specified
CNA Linux Linux affected 3.0 Not specified
CNA Linux Linux unaffected 3.0 semver Not specified
CNA Linux Linux unaffected 5.10.261 5.10.* semver Not specified
CNA Linux Linux unaffected 5.15.212 5.15.* semver Not specified
CNA Linux Linux unaffected 6.1.178 6.1.* semver Not specified
CNA Linux Linux unaffected 6.6.145 6.6.* semver Not specified
CNA Linux Linux unaffected 6.12.97 6.12.* semver Not specified
CNA Linux Linux unaffected 6.18.40 6.18.* semver Not specified
CNA Linux Linux unaffected 7.1.5 7.1.* semver Not specified
CNA Linux Linux unaffected 7.2-rc4 * original_commit_for_fix Not specified

References

ReferenceSourceLinkTags
git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report