CVE-2026-10664: memory-safety in zephyrproject zephyr
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.
AI Analysis
Technical Summary
CVE-2026-10664 is a memory safety vulnerability in the nRF70 Wi-Fi driver's power-save event handler function nrf_wifi_event_proc_get_power_save_info() within Zephyr OS releases through version 4.4.0. The function copies TWT flow entries from an event into a fixed-size array of 8 elements without validating the number of flows against the array size or the event length. If the event reports more than 8 flows, the handler writes beyond the bounds of the destination array, which is typically located on the caller's stack, causing an out-of-bounds write of approximately 40 bytes. The event is generated by the nRF70 co-processor firmware in response to a host-initiated power-save GET request, so exploitation requires the firmware to send a malformed or out-of-range event. The trust boundary is between the host and the trusted co-processor, not directly from a remote access point. The vulnerability is mitigated by rejecting events with num_twt_flows greater than WIFI_MAX_TWT_FLOWS or with event length shorter than expected, and by adding a null check on the caller buffer.
Potential Impact
The vulnerability allows an out-of-bounds write on the stack of the caller, potentially leading to memory corruption affecting confidentiality, integrity, and availability. However, exploitation requires a malformed event from the trusted nRF70 co-processor firmware, limiting the attack surface. The CVSS 3.1 score is 5.0 (medium severity) reflecting the complexity and limited attack vector. There are no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves rejecting events where the number of TWT flows exceeds the maximum allowed or where the event length is insufficient, and adding a null check on the caller buffer. Until an official patch is available, ensure that the nRF70 co-processor firmware is trusted and not compromised, as the vulnerability requires malformed events from this firmware.
CVE-2026-10664: memory-safety in zephyrproject zephyr
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.
CVSS v3.1
Score 5.0medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-10664 is a memory safety vulnerability in the nRF70 Wi-Fi driver's power-save event handler function nrf_wifi_event_proc_get_power_save_info() within Zephyr OS releases through version 4.4.0. The function copies TWT flow entries from an event into a fixed-size array of 8 elements without validating the number of flows against the array size or the event length. If the event reports more than 8 flows, the handler writes beyond the bounds of the destination array, which is typically located on the caller's stack, causing an out-of-bounds write of approximately 40 bytes. The event is generated by the nRF70 co-processor firmware in response to a host-initiated power-save GET request, so exploitation requires the firmware to send a malformed or out-of-range event. The trust boundary is between the host and the trusted co-processor, not directly from a remote access point. The vulnerability is mitigated by rejecting events with num_twt_flows greater than WIFI_MAX_TWT_FLOWS or with event length shorter than expected, and by adding a null check on the caller buffer.
Potential Impact
The vulnerability allows an out-of-bounds write on the stack of the caller, potentially leading to memory corruption affecting confidentiality, integrity, and availability. However, exploitation requires a malformed event from the trusted nRF70 co-processor firmware, limiting the attack surface. The CVSS 3.1 score is 5.0 (medium severity) reflecting the complexity and limited attack vector. There are no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves rejecting events where the number of TWT flows exceeds the maximum allowed or where the event length is insufficient, and adding a null check on the caller buffer. Until an official patch is available, ensure that the nRF70 co-processor firmware is trusted and not compromised, as the vulnerability requires malformed events from this firmware.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-02T15:25:25.070Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a54991068715ace436e94d8
Added to database: 07/13/2026, 07:51:44 UTC
Last enriched: 07/20/2026, 19:10:23 UTC
Last updated: 08/27/2026, 22:52:08 UTC
Views: 98
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.