# CVE-2026-93802: wifi: rsi: validate beacon length before fixed buffer copy

> A buffer overflow in the Linux kernel RSI WiFi driver allows attackers to cause denial of service or execute code via crafted beacon frames.

- **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-103751, BELL-CVE-2026-93802, DEBIAN-CVE-2026-93802, GHSA-5x9j-5x5g-gr56, UBUNTU-CVE-2026-93802

## What is CVE-2026-93802?

CVE-2026-93802 is a memory corruption 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: validate beacon length before fixed buffer copy

rsi_prepare_beacon() copies the mac80211 beacon frame after
FRAME_DESC_SZ into a management skb whose usable tailroom may be smaller
than MAX_MGMT_PKT_SIZE after alignment.

Validate the beacon length against the actual tailroom before the copy
and skb_put(). Leave ownership of the management skb with the caller on
error, matching the existing rsi_send_beacon() cleanup path.

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


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

Apply the vendor's patch.

## Is CVE-2026-93802 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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