# CVE-2026-93807: wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers

> An attacker within WiFi range can read out-of-bounds memory from the kernel by exploiting a flaw in the RSI WiFi driver's key handling logic.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103649, BELL-CVE-2026-93807, DEBIAN-CVE-2026-93807, GHSA-3mp2-v334-gxv5, UBUNTU-CVE-2026-93807

## What is CVE-2026-93807?

CVE-2026-93807 is a 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: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers

rsi_hal_load_key() copies tx_mic_key and rx_mic_key from data[16] and
data[24] whenever key data is present. Those offsets are only part of
the 32-byte TKIP key layout. Shorter keys used by other ciphers, such as
CCMP, do not provide those bytes, so the unconditional copies can read
past the supplied key buffer.

Only copy the MIC keys for TKIP, and reject malformed TKIP keys that are
shorter than the expected 32-byte layout.

[drop useless length check]

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


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

Apply the vendor's patch.

## Is CVE-2026-93807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93807 is a 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-93807 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-93807/ (Markdown: https://insights.sbomify.com/CVE-2026-93807/index.md)
```

## Sources

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

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