# CVE-2026-10664: Out-of-bounds write in nRF70 Wi-Fi driver power-save event handler (unbounded TWT flow count)

> Out-of-bounds write in nRF70 Wi-Fi driver allows memory corruption if coprocessor firmware sends malformed power-save events, requiring CONFIG_NRF70_STA_MODE.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-3r6j-pm38-r43m

## What is CVE-2026-10664?

CVE-2026-10664 is a medium-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 12 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The nRF70 Wi-Fi driver's power-save event handler nrf_wifi_event_proc_get_power_save_info() in drivers/wifi/nrf_wifi/src/wifi_mgmt.c copied TWT (Target Wake Time) flow entries from an nrf_wifi_umac_event_power_save_info event into the fixed-size twt_flows[WIFI_MAX_TWT_FLOWS] (8-element) array of a caller-supplied struct wifi_ps_config, looping over event-provided num_twt_flows without validating it against WIFI_MAX_TWT_FLOWS or checking event_len. When num_twt_flows exceeds 8, the handler writes past the destination array (which is typically on the caller's stack, e.g. the wifi ps shell command) -- an out-of-bounds write of ~40-byte TWT entries -- and reads twt_flow_info[i] past the event buffer. The event is delivered by the nRF70 co-processor firmware in response to a host-initiated power-save GET, so reaching the overflow requires the firmware to emit a malformed or out-of-range event; the trust boundary is host-to-trusted-coprocessor rather than a direct remote-AP write, with over-the-air influence on the flow count being indirect and bounded by the 3-bit TWT flow-id space. Affected: builds with CONFIG_NRF70_STA_MODE on releases through v4.4.0. The fix rejects events with num_twt_flows > WIFI_MAX_TWT_FLOWS or with event_len shorter than the claimed entries, and adds a NULL check on the caller buffer.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Zephyrproject Zephyr.

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

No fix has been published for CVE-2026-10664 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10664 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10664 exists.

## Other vulnerabilities in Zephyrproject Zephyr

- [CVE-2026-5067](https://insights.sbomify.com/CVE-2026-5067/): Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key (critical 9.8)
- [CVE-2022-3806](https://insights.sbomify.com/CVE-2022-3806/): Bluetooth HCI Error Handling Double Free (critical 9.8)
- [CVE-2017-14199](https://insights.sbomify.com/CVE-2017-14199/): Memory corruption in getaddrinfo (critical 9.8)
- [CVE-2018-1000800](https://insights.sbomify.com/CVE-2018-1000800/): Null dereference in n/a (critical 9.8)
- [CVE-2021-3329](https://insights.sbomify.com/CVE-2021-3329/): DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10664 is a medium-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 12 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10664 exists.

Affected product: Zephyrproject Zephyr. 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-10664/ (Markdown: https://insights.sbomify.com/CVE-2026-10664/index.md)
```

## Sources

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

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