VulnerabilityPublished 25 Jul 2026Updated 6 Nov 2026

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

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in d16713c06006669c7162dfab1cedf4cb24429311 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in d16713c06006669c7162dfab1cedf4cb24429311, 351dd7d2c80d23e56dcce6faa4e62bea5b0877c7, 77e7b127472a191e086e1e0b1b051703f33b1801

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to d16713c06006669c7162dfab1cedf4cb24429311, 351dd7d2c80d23e56dcce6faa4e62bea5b0877c7 or 77e7b127472a191e086e1e0b1b051703f33b1801.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 8aa2f59260eb66fc80378c158922ccb741ccc491, < d16713c06006669c7162dfab1cedf4cb24429311	Fixed in d16713c06006669c7162dfab1cedf4cb24429311
LinuxLinux	Affected ≥ 8aa2f59260eb66fc80378c158922ccb741ccc491, < 351dd7d2c80d23e56dcce6faa4e62bea5b0877c7	Fixed in 351dd7d2c80d23e56dcce6faa4e62bea5b0877c7
LinuxLinux	Affected ≥ 8aa2f59260eb66fc80378c158922ccb741ccc491, < 77e7b127472a191e086e1e0b1b051703f33b1801	Fixed in 77e7b127472a191e086e1e0b1b051703f33b1801
LinuxLinux	Affected =6.14	Fixed in–

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

References

Community reviews

Loading reviews…