dbcve.org
VulnerabilityAwaiting classification

CVE-2026-63832

HIGH · 8.8 CVSS v3.1 Published 2026-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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]

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel mt76 wireless driver, mt76_sta_add was reinitializing the wcid->poll_list without checking if the wcid was already published by mt7925_mac_sta_add. This caused a double-add to the sta_poll_list, resulting in list_add corruption where a list entry's prev->next pointer pointed to itself instead of the correct next element.

MitigationApply the kernel patch that adds a publish check in mt76_sta_add to prevent reinitializing an already-published wcid->poll_list; this requires updating the Linux kernel or the affected wireless driver module.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify mt76 wifi driver is in use
    Run 'lsmod | grep mt76' or check kernel config with 'zcat /proc/config.gz | grep MT76' or check /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek/mt76 for mt76 driver files
    Affected if The mt76 driver module is loaded or built into the kernel, indicating the affected component is present
  2. Confirm mt7925 driver or device is present
    Run 'lspci | grep -i mediatek' or 'lsusb' or check 'ip link' for wireless interfaces managed by mt7925/mt76 devices
    Affected if A wireless device using the mt7925 or related mt76 driver is present and active
  3. Check kernel source for vulnerable function
    Examine the mt76_sta_add function in the kernel source (drivers/net/wireless/mediatek/mt76/mac80211.c or similar) to see if it contains the poll_list initialization without the wcid publish check
    Affected if The vulnerable code pattern (wcid->poll_list initialization without checking wcid->publiished flag) exists in the installed kernel source
  4. Compare kernel version against patch date
    Run 'uname -r' and cross-reference with kernel versions that include the fix (typically the patch was merged in kernel 6.x after the vulnerability discovery)
    Affected if The running kernel predates the patch that adds the wcid publish check in mt76_sta_add
  5. Monitor for list corruption symptoms
    Check dmesg for 'list_add corruption' or 'bad next/prev pointers' messages, or use tools like 'slub_debug=P' to enable slab debugging and look for memory corruption in wireless driver allocations
    Affected if List corruption warnings appear in kernel logs related to wcid or sta_poll_list structures

A system is affected if it runs a Linux kernel with the mt76 driver (particularly mt7925) where mt76_sta_add initializes wcid->poll_list without first checking if wcid->published is already set, allowing the vulnerable code path to execute.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the kernel patch that adds a publish check in mt76_sta_add to prevent reinitializing an already-published wcid->poll_list; this requires updating the Linux kernel or the affected wireless driver module.

Recommended fix Moderate confidence

Linux kernel version subsequent to 7.1-rc4 (any stable release containing the mt76 wcid publish check fix)

  1. Upgrade the Linux kernel to a version that includes the fix for the mt76 wcid publish check issue. The fix was introduced to address sta_poll_list corruption in the mt7925 wireless driver.
  2. Verify the kernel version includes the specific commit that adds wcid publish check in mt76_sta_add. This commit prevents reinitializing the wcid->poll_list when wcid has already been published by mt7925_mac_sta_add.
  3. After kernel upgrade, monitor wireless functionality to confirm the list_add corruption no longer occurs during authentication/reassociation events with mt7925 devices.
Caveat Kernel upgrades carry standard risks; ensure wireless driver compatibility with the new kernel version before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,320
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-63832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-63832 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data