CVE-2026-98705: Linux kernel · wifi: mac80211: account proxy paths against the mesh path limit
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in df072db65fdaa34ad15e1d66fc06a53e3e97f778 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in df072db65fdaa34ad15e1d66fc06a53e3e97f778, c66ab4b94bb04c162485759196555e08c0965320, a5f35d4b112af1415ff06bd501c8cc26cc08aa8b +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: account proxy paths against the mesh path limit Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS. mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged. mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds. Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.
References
- git.kernel.org/stable/c/c66ab4b94bb04c162485759196555e08c0965320 (opens in a new tab)
- git.kernel.org/stable/c/df072db65fdaa34ad15e1d66fc06a53e3e97f778 (opens in a new tab)
- git.kernel.org/stable/c/3b75831ceee76d32bb8e7ddd241904f92f9b5407 (opens in a new tab)
- git.kernel.org/stable/c/5a32409ed34a1868830899a5d2437f0b3bf3532c (opens in a new tab)
- git.kernel.org/stable/c/a5f35d4b112af1415ff06bd501c8cc26cc08aa8b (opens in a new tab)