# CVE-2026-98193: wifi: libipw: reject TKIP frames without a full MIC

> A missing check in the Linux kernel WiFi driver allows out-of-bounds reads via short TKIP frames, potentially causing crashes or code execution.

- **Severity:** Not scored
- **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:** 6 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-106161, BELL-CVE-2026-98193, DEBIAN-CVE-2026-98193, GHSA-8rh9-27vf-9cwr, UBUNTU-CVE-2026-98193

## What is CVE-2026-98193?

CVE-2026-98193 is a memory corruption vulnerability in Linux, published on 6 Oct 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: libipw: reject TKIP frames without a full MIC

libipw_michael_mic_verify() assumes that an skb contains an eight-byte
Michael MIC. A short TKIP frame makes the unsigned payload length wrap,
causing michael_mic() to read past the skb.

Check that the MIC is present before verifying it, and use the existing
MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.

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


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

Apply the vendor's patch.

## Is CVE-2026-98193 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98193 is a memory corruption vulnerability in Linux, published on 6 Oct 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-98193 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-98193/ (Markdown: https://insights.sbomify.com/CVE-2026-98193/index.md)
```

## Sources

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

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