# CVE-2026-98407: wifi: rsi: fix heap OOB write on key removal

> Heap out-of-bounds write in Linux kernel RSI WiFi driver during key removal allows attackers to corrupt memory, potentially leading to code execution or system crashes.

- **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:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108116, BELL-CVE-2026-98407, DEBIAN-CVE-2026-98407, GHSA-5p9q-rqwh-2www, UBUNTU-CVE-2026-98407

## What is CVE-2026-98407?

CVE-2026-98407 is a memory corruption vulnerability in Linux, published on 14 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: rsi: fix heap OOB write on key removal

When a key is removed (data == NULL), rsi_hal_load_key() runs:

	memset(&set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);

set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &set_key[FRAME_DESC_SZ] is
skb->data + 2560, and the memset writes 144 zero bytes starting
2.4KB past the end of the 160-byte skb data buffer, corrupting
unrelated heap objects. The intended byte offset would have been
(u8 *)set_key + FRAME_DESC_SZ.

The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.

The memset is redundant: the whole buffer is zeroed right after
allocation, so the frame sent to the device is byte-identical
without it. Drop the else branch; normal operation is unaffected.

Discovered by Atuin - Automated Vulnerability Discovery Engine.

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


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

Apply the vendor's patch.

## Is CVE-2026-98407 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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