# CVE-2026-74324: wifi: mt76: mt7925: validate skb length in testmode query

> A local attacker with testmode access can read kernel memory via an out-of-bounds read in the mt7925 WiFi driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-74324, DEBIAN-CVE-2026-74324, GHSA-22xx-mmhm-wq6h, UBUNTU-CVE-2026-74324

## What is CVE-2026-74324?

CVE-2026-74324 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: mt7925: validate skb length in testmode query

In mt7925_tm_query(), the response skb from mt76_mcu_send_and_get_msg()
is used in a memcpy without validating its length:

  memcpy(evt_resp, skb->data + 8, MT7925_EVT_RSP_LEN);

where MT7925_EVT_RSP_LEN is 512. If the firmware returns a response
shorter than 520 bytes (8 + 512), this reads beyond the skb data
buffer. The over-read data is then returned to userspace via nla_put()
in mt7925_testmode_dump().

Add a length check before the memcpy to ensure the skb contains
sufficient data.

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


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

Apply the vendor's patch.

## Is CVE-2026-74324 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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