# CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access

> A missing length check in the Linux kernel WiFi driver allows attackers to cause a denial of service via malformed association response frames.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103730, BELL-CVE-2026-93806, DEBIAN-CVE-2026-93806, GHSA-73rr-rqr3-fp7p, UBUNTU-CVE-2026-93806

## What is CVE-2026-93806?

CVE-2026-93806 is a high-severity vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: cfg80211: validate assoc response length before status and IE access

cfg80211_rx_assoc_resp() initialises the status and response-IE fields
of cfg80211_connect_resp_params from the management frame before
proving that the frame is long enough for those offsets. S1G and
regular association responses also have different IE offsets, but the
S1G path only patched resp_ie after the unsafe initialiser had already
run.

Defer resp_ie, resp_ie_len, and status to after the link-iteration
loop. Use a bool to remember whether the frame is S1G, then validate
the appropriate minimum length and set all three fields in a single
if/else block. Funnel short-frame and SME-reject cleanup through a
shared free_bss label for the abandon paths.

## Which versions are affected by CVE-2026-93806?


## How do I fix CVE-2026-93806?

Apply the vendor's patch.

## Is CVE-2026-93806 being exploited?

There is no known exploitation of CVE-2026-93806 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93806 and fix it if it is affected.

What it is: CVE-2026-93806 is a high-severity vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93806 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93806/ (Markdown: https://insights.sbomify.com/CVE-2026-93806/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93806
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93806
- OSV: https://osv.dev/vulnerability/CVE-2026-93806

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93806/
Summaries are generated and may contain mistakes; the official description above is the record.