wifi: mac80211: account proxy paths against the mesh path limit
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ece1a2e7e86078c8379937b546e32cb7f25fcb6c · < 3b75831ceee76d32bb8e7ddd241904f92f9b5407| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel’s mac80211 mesh code, removing or expiring proxy paths can make the shared path counter inaccurate. Proxy-path churn can then allow mesh path additions beyond the 1024-entry limit. The input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with mac80211 mesh networking should check whether their kernel includes the fix; affected versions were not provided.