Live › vulnerability › CVE-2026-98958
Go to dashboardIn the Linux kernel's mt76 Wi-Fi driver, frames sent on one link of a multi-link (MLO) peer can be counted against a different link than the one that completes them, so the counter drifts upward until the station is blocked. The sources describe a denial-of-service effect on wireless traffic, not code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the mt76 Wi-Fi driver and MLO-capable peers, such as MediaTek-based Wi-Fi 7 hardware on Linux access points or clients. Systems without mt76 hardware, or without multi-link Wi-Fi, are unlikely to be affected. The sources do not say which kernel versions are affected.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: account non-AQL frames per peer rather than per link
The driver increments wcid->non_aql_packets when a frame goes to the hardware queue. The completion path decrements the counter again.
For an MLO peer, the hardware reports the completion on the link that it used for the transmission. This link can differ from the link that the driver queued the frame on. In that case, the increment and the decrement go to different link wcids, and the count drifts upwards until it blocks the station.
Keep the count on the wcid of the primary link, like the other peer-wide state.
This page as .md · .json · in your agent: get_signal("CVE-2026-98958")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.