# CVE-2026-90357: wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement

> A use-after-free vulnerability in the Linux kernel mt7915 WiFi driver allows attackers to corrupt memory, potentially leading to code execution or system crashes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-103011, BELL-CVE-2026-90357, DEBIAN-CVE-2026-90357, GHSA-9px9-hrqm-cp96, UBUNTU-CVE-2026-90357

## What is CVE-2026-90357?

CVE-2026-90357 is a high-severity use after free 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: mt7915: unlink TWT flow if the MCU rejects the agreement

The flow is added to dev->twt_list before sending the agreement to the
firmware, but the error path leaves it linked while flowid_mask is
never set. The flow slot can then be reused and memset while still on
the list, corrupting twt_list, and station removal leaves a dangling
entry behind that mt7915_mac_twt_sched_list_add() later walks.

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


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

Apply the vendor's patch.

## Is CVE-2026-90357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90357 is a high-severity use after free 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-90357 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-90357/ (Markdown: https://insights.sbomify.com/CVE-2026-90357/index.md)
```

## Sources

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

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