# CVE-2026-68469: wifi: mwifiex: fix permanently busy scans after multiple roam iterations

Status: published. Published: 2026-08-15. Updated: 2026-11-06.

In 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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < 2ed36b2586f16c480ed58de303af704c2235e16d (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < 5796eabe435d83544b6fe39851ce47ca68fdb778 (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < 31a2c409f8f58d20f0f6391c151421155768ed77 (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < deb5f0ae384f1cf41fccaf6375266db2f2911b2b (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < 1bc55db2d34756bd53e4460dbb699619ee13cd7f (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < a59cfa165aee3e29d06145041c0ebe46a51de604 (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < 6126e12bf8c87badeab41a164c9689ac88e5c160 (affected, git); ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e; < d78a407bad6f500884a8606aea1a5a9207be4030 (affected, git). Source: CNA: Linux
- Linux / Linux: 3.0 (affected); ≥ 0; < 3.0 (unaffected, semver); ≥ 5.10.261; ≤ 5.10.* (unaffected, semver); ≥ 5.15.212; ≤ 5.15.* (unaffected, semver); ≥ 6.1.178; ≤ 6.1.* (unaffected, semver); ≥ 6.6.145; ≤ 6.6.* (unaffected, semver); ≥ 6.12.97; ≤ 6.12.* (unaffected, semver); ≥ 6.18.40; ≤ 6.18.* (unaffected, semver); ≥ 7.1.5; ≤ 7.1.* (unaffected, semver); ≥ 7.2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.26% as of 2026-11-06; percentile 18.28%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d (CNA: Linux)

- https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778 (CNA: Linux)

- https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77 (CNA: Linux)

- https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b (CNA: Linux)

- https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f (CNA: Linux)

- https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604 (CNA: Linux)

- https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160 (CNA: Linux)

- https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030 (CNA: Linux)

- https://git.kernel.org/stable/c/1bc55db2d34756bd53e4460dbb699619ee13cd7f (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/2ed36b2586f16c480ed58de303af704c2235e16d (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/31a2c409f8f58d20f0f6391c151421155768ed77 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/5796eabe435d83544b6fe39851ce47ca68fdb778 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/6126e12bf8c87badeab41a164c9689ac88e5c160 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/a59cfa165aee3e29d06145041c0ebe46a51de604 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/d78a407bad6f500884a8606aea1a5a9207be4030 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/deb5f0ae384f1cf41fccaf6375266db2f2911b2b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-68469; retrieved 2026-11-06; source updated 2026-11-06

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68469; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-68469; retrieved 2026-11-06; source updated Not reported

Revision: c4428c04b3e989195366e39942e456aff805fee4e999d292258c290894f0e8c7

Canonical: https://y2.dev/cve/CVE-2026-68469

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.