VulnerabilityPublished 23 Oct 2026

CVE-2026-98958: Linux kernel · wifi: mt76: account non-AQL frames per peer rather than per link

Affects Linux kernelSource CVE Database V5

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

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e0f2ae4a7539454ec50c353571779fcda8c0cfcf, 752770d7a58c821c17909c3ca67f9f14ab146a40, 9f28f504650869d41f7b3e98e4bc4547af4d5670

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 e0f2ae4a7539454ec50c353571779fcda8c0cfcf, 752770d7a58c821c17909c3ca67f9f14ab146a40 or 9f28f504650869d41f7b3e98e4bc4547af4d5670.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 86c051f2c418abd7eefd8c545a01bdffd220cb95, < e0f2ae4a7539454ec50c353571779fcda8c0cfcf	Fixed in e0f2ae4a7539454ec50c353571779fcda8c0cfcf
LinuxLinux	Affected ≥ 86c051f2c418abd7eefd8c545a01bdffd220cb95, < 752770d7a58c821c17909c3ca67f9f14ab146a40	Fixed in 752770d7a58c821c17909c3ca67f9f14ab146a40
LinuxLinux	Affected ≥ 86c051f2c418abd7eefd8c545a01bdffd220cb95, < 9f28f504650869d41f7b3e98e4bc4547af4d5670	Fixed in 9f28f504650869d41f7b3e98e4bc4547af4d5670
LinuxLinux	Affected =6.11	Fixed in–

Description

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.

References

Community reviews

Loading reviews…