# CVE-2026-68311: wifi: mt76: mt7925: guard link STA in decap offload

> A NULL pointer dereference in the Linux kernel mt7925 WiFi driver allows attackers to cause a system crash via crafted wireless traffic.

- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68311, DEBIAN-CVE-2026-68311, GHSA-r4m3-927r-4wxc, UBUNTU-CVE-2026-68311

## What is CVE-2026-68311?

CVE-2026-68311 is a vulnerability in Linux, published on 10 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: mt7925: guard link STA in decap offload

mt7925_sta_set_decap_offload() iterates over the vif valid_links mask
when updating decap offload state for an MLO station. The station may not
have a link STA for every valid link of the vif, so mt792x_sta_to_link()
can return NULL for a link that belongs to the vif but not to the station.

The function currently dereferences mlink before checking whether the
link WCID is ready. If mlink is NULL, setting or clearing
MT_WCID_FLAG_HDR_TRANS dereferences a NULL pointer.

Skip links without a station link before touching mlink->wcid.

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


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

Apply the vendor's patch.

## Is CVE-2026-68311 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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