# CVE-2026-14366: SiWx91x WiFi driver double-unref / use-after-free of caller-owned TX net_pkt

> A use-after-free in the SiWx91x WiFi driver allows remote attackers to cause denial of service or potential code execution via crafted network traffic.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **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:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-f9qq-jv4w-pqxg

## What is CVE-2026-14366?

CVE-2026-14366 is a medium-severity use after free vulnerability in zephyrproject zephyr, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Silicon Labs SiWx917 WiFi driver's transmit callback siwx91x_send() in drivers/wifi/siwx91x/siwx91x_wifi.c frees a network packet it does not own. In the Zephyr TX path the net_pkt is owned by the L2/networking stack; the driver only borrows it to copy the frame bytes into a local net_buf. Before the fix, after transmitting, siwx91x_send() additionally called net_pkt_unref(pkt) on the caller-owned packet, dropping its last reference and returning it to the shared packet pool prematurely. This code path is compiled in by default (CONFIG_WIFI_SILABS_SIWX91X_NET_STACK_NATIVE).

The caller, ethernet_send() in subsys/net/l2/ethernet/ethernet.c, keeps using the packet after the driver returns: it reads net_pkt_get_len(pkt), updates TX statistics, and then performs its own net_pkt_unref(pkt). Because the driver already released the packet, these are use-after-free reads followed by a second unref (a double free). When concurrent network activity recycles the freed slab slot between the two unrefs, the trailing unref decrements a different, live packet's reference count and frees it, corrupting the net_pkt pool shared by both the receive and transmit paths.

The defect is exercised by ordinary transmission over the native-stack SiWx917 WiFi interface, and an adjacent attacker on the same WiFi network can induce transmissions (for example ARP or ICMP echo replies, or TCP handshakes) to drive the path. The primary observable impact is loss of availability (transmit hangs and crashes from pool corruption), with race-dependent memory corruption of the kernel networking buffer pool. The fix removes the erroneous net_pkt_unref(pkt) from siwx91x_send(); the driver's receive-path unref, which correctly frees a packet the driver itself allocated, is unaffected.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-14366 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14366 is a medium-severity use after free vulnerability in zephyrproject zephyr, published on 31 Aug 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-14366 in the wild and no public exploit code.

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-14366/ (Markdown: https://insights.sbomify.com/CVE-2026-14366/index.md)
```

## Sources

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

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