# CVE-2026-93793: wifi: iwlwifi: mvm: validate TX_CMD response layout

> A missing validation in the iwlwifi driver allows malformed TX_CMD responses to cause a denial of service.

- **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:** 21 Oct 2026
- **Also known as:** AZL-103553, BELL-CVE-2026-93793, DEBIAN-CVE-2026-93793, GHSA-cv3p-w443-82hj, UBUNTU-CVE-2026-93793

## What is CVE-2026-93793?

CVE-2026-93793 is a high-severity denial of service 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: iwlwifi: mvm: validate TX_CMD response layout

TX_CMD parsing uses frame_count to walk status entries and then
read the trailing SCD SSN. Make the minimum-length check follow
that exact runtime layout calculation before parsing the payload.

For new TX API, reject TX_CMD responses with frame_count != 1 and
warn/return in the aggregation handler to document that aggregated
accounting is expected via BA notifications.

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


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

Apply the vendor's patch.

## Is CVE-2026-93793 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93793 is a high-severity denial of service 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-93793 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-93793/ (Markdown: https://insights.sbomify.com/CVE-2026-93793/index.md)
```

## Sources

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

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