CVE-2026-63832
Linux mt76 (mt7925) Wi‑Fi driver list corruption causing kernel memory corruption.
Is CVE-2026-63832 being exploited?
Not confirmed. CVE-2026-63832 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-63832?
CVE-2026-63832 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63832?
Yes. A fix has been recorded for CVE-2026-63832. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63832 affect?
CVE-2026-63832 affects Linux kernel (mt76 driver), MediaTek mt7925-based devices, Wireless stacks using mt76/mt7925. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63832?
Update Linux kernel to versions containing the mt76/mt7925 fix and apply vendor firmware updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted Wi‑Fi frames can trigger kernel list/memory corruption, causing DoS and potential local privilege escalation.
Patch when possible
- affected>= 4911e4cb157cf87d5bdb3fa8e0c200032443371e and < 3c499851753a24d2e148d4e9ca51764c0c51554e
- affected>= 4911e4cb157cf87d5bdb3fa8e0c200032443371e and < 55e014aaec650ede08b693ba59c8d0443f13f11c
- affected>= 4911e4cb157cf87d5bdb3fa8e0c200032443371e and < 20b126920a259df4d7dcae19fcfe2c57a74d6b2e
- affectedc9389e3f9453ec2d710e61830eafedddfd561226
- affected57d3f833087942ded1a8765b1b361454d3d39e8f
- affected>= 6.12.13 and < 6.13
- affected>= 6.13.2 and < 6.14
- affected6.14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.