# CVE-2026-68310: wifi: mt76: mt7915: guard HE capability lookups

> A null pointer dereference in the mt7915 Wi-Fi driver can cause a kernel crash when handling specific HE capability lookups.

- **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:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68310, DEBIAN-CVE-2026-68310, GHSA-wpgr-w4wr-692g, UBUNTU-CVE-2026-68310

## What is CVE-2026-68310?

CVE-2026-68310 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: mt7915: guard HE capability lookups

mt7915_mcu_bss_he_tlv() and mt7915_mcu_sta_bfer_tlv() both run after
checking HE support, then dereference the HE PHY capability returned by
mt76_connac_get_he_phy_cap(). That helper can return NULL when no
capability entry matches the vif type.

Fetch the capability before appending the TLV and skip the HE-specific
setup when no matching capability is available.

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


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

Apply the vendor's patch.

## Is CVE-2026-68310 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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