{"id":"CVE-2026-68469","title":"wifi: mwifiex: fix permanently busy scans after multiple roam iterations","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mwifiex: fix permanently busy scans after multiple roam iterations\n\nIn order for the firmware to sleep, the driver has to confirm a\npreviously received sleep requ…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 2ed36b2586f16c480ed58de303af704c2235e16d","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 5796eabe435d83544b6fe39851ce47ca68fdb778","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 31a2c409f8f58d20f0f6391c151421155768ed77","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < deb5f0ae384f1cf41fccaf6375266db2f2911b2b","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 1bc55db2d34756bd53e4460dbb699619ee13cd7f","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < a59cfa165aee3e29d06145041c0ebe46a51de604","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 6126e12bf8c87badeab41a164c9689ac88e5c160","Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < d78a407bad6f500884a8606aea1a5a9207be4030","Linux 3.0"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-06T16:49:59.702038Z"},"published":"2026-08-15","updated":"2026-11-06","sourceUpdated":"2026-11-06T16:55:17.491Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-68469","references":[{"url":"https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d"},{"url":"https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778"},{"url":"https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77"},{"url":"https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b"},{"url":"https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f"},{"url":"https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604"},{"url":"https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160"},{"url":"https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030"}],"tags":["cve.org"],"epss":0.00263,"epssPercentile":0.18288,"ingestedAt":"2026-11-06T18:00:12.601Z","slug":"CVE-2026-68469","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mwifiex: fix permanently busy scans after multiple roam iterations\n\nIn order for the firmware to sleep, the driver has to confirm a\npreviously received sleep request. The normal sequence of evets goes\nlike this:\nEVENT_SLEEP -> adapter->ps_state = PS_STATE_PRE_SLEEP -> sleep-confirm\n-> SLEEP -> EVENT_AWAKE -> AWAKE.\nBefore sending the sleep-confirm command, the driver must make sure\nthere are no commands either running or waiting to be completed.\n\nmwifiex_ret_802_11_associate() unconditionally sets\nps_state = PS_STATE_AWAKE when it processes the association command\nresponse, outside of the normal powersave management flow. If\nEVENT_SLEEP arrives while the association command is in flight,\nps_state is PRE_SLEEP when the association command response is parsed,\nand the forced AWAKE overwrites it. The deferred sleep-confirm is\nnever sent.\n\nA subsequent scan_start command is correctly acknowledged, but the\nfirmware doesn't generate scan_result events. The scan request never\nfinishes, and additional requests from userspace fail with -EBUSY.\n\nAfter testing on both IW412 and W8997, I could only trigger the bug on\nthe IW412 and observed the firmwares behave differently. On the IW412\nthe firmware still sends EVENT_SLEEP while the authentication /\nassociation process is ongoing. A W8997 under the same\nconditions seems to suppress power-save for the duration of the\nassociation, so PRE_SLEEP never coincided with the association response\neven after extended periods of testing using the loops\ndescribed below (>12hours).\n\nOn the IW412, the delay between commands that triggers an EVENT_SLEEP\nwas empirically determined to be ~20ms. This delay can naturally occur\nwhen the driver is outputting debugging information\n(debug_mask = 0x00000037), in which situation the busy scans issue is\nrepeatable while running \"test 1)\" as described below. If the delay\nbetween commands is less than ~20ms, the firmware stays awake and\nthe issue was not reproducible running the same test.\n\nThe host_mlme=false path also behaves differently. In this case, the\nentire authentication / association transaction is executed by one\ncommand (HostCmd_CMD_802_11_ASSOCIATE), and the firmware doesn't emit\nEVENT_SLEEP while the command is running.\n\nRemove the assignment so the ps_state is only manipulated in the paths\nthat are related to powersave event handling and on the main workqueue\nfor correct sleep confirmation.\n\nThe following loop tests were performed (with debugging output enabled):\n1) force roaming between two AP's, one 5GHz and one 2.4GHz, same\nSSID. Use wpa_cli to trigger the roaming behavior, sleep 2s\nbetween iterations.\n2) force a disconnection to AP 1 and a connection to AP 2, test\nscan. Use wpa_cli to trigger the connection changes, sleep 2s\nbetween iterations.\n\nEach test ran in each device for at least 3 hours.\n\n## Affected\n\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 2ed36b2586f16c480ed58de303af704c2235e16d`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 5796eabe435d83544b6fe39851ce47ca68fdb778`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 31a2c409f8f58d20f0f6391c151421155768ed77`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < deb5f0ae384f1cf41fccaf6375266db2f2911b2b`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 1bc55db2d34756bd53e4460dbb699619ee13cd7f`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < a59cfa165aee3e29d06145041c0ebe46a51de604`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < 6126e12bf8c87badeab41a164c9689ac88e5c160`\n- `Linux >= 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e < d78a407bad6f500884a8606aea1a5a9207be4030`\n- `Linux 3.0`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}