# CVE-2026-74322: wifi: mt76: mt7996: Fix possible NULL pointer dereference in mt7996_mac_write_txwi_80211()

> A NULL pointer dereference in the mt7996 WiFi driver allows local attackers to cause a system crash via crafted injected 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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74322, DEBIAN-CVE-2026-74322, GHSA-xpxx-w558-6w56, UBUNTU-CVE-2026-74322

## What is CVE-2026-74322?

CVE-2026-74322 is a vulnerability in Linux, published on 15 Aug 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: mt7996: Fix possible NULL pointer dereference in mt7996_mac_write_txwi_80211()

For injected frames (e.g. via radiotap), mac80211 can pass
info->control.vif = NULL, as explicitly noted in struct ieee80211_tx_info.
Check vif pointer before executing ieee80211_vif_is_mld() in
mt7996_mac_write_txwi_80211 routine in order to avoid a possible NULL
pointer dereference.

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


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

Apply the vendor's patch.

## Is CVE-2026-74322 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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