# CVE-2026-90378: wifi: mt76: mt792x: Fix memory leak in SDIO TX path

> A memory leak in the Linux kernel mt792x WiFi driver allows attackers to cause denial of service by sending zero-length frames.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102897, BELL-CVE-2026-90378, DEBIAN-CVE-2026-90378, GHSA-v25j-v9cr-gcjm, UBUNTU-CVE-2026-90378

## What is CVE-2026-90378?

CVE-2026-90378 is a memory corruption vulnerability in Linux, published on 17 Sep 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: mt76: mt792x: Fix memory leak in SDIO TX path

When tx_prepare_skb() returns an error in the SDIO TX path, the
skb is not freed, leading to a memory leak. This can occur when
zero-length frames (such as WNM NULL frames) are dropped to prevent
potential hardware TX hangs.

Fix this by properly releasing the skb with ieee80211_tx_status_ext()
when tx_prepare_skb() fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-90378 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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