From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0A9333CB8E5 for ; Sun, 18 Oct 2026 15:54:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792338868; cv=none; b=bZrZZOVsHIWBPz5jP5M2T5z4qwBG4KrzIU4GRs6afp+T37ZmNIF0prLOmPuok0FsVJ6oVskqLzL/+iQSYQk73dGOkQN868rJfykn3GNi0aWdSxVrMzC3xQBpGMnyMUfuTtSB+2pOHxWtEeoLY5lWIw5p1UgCKo3653b8FHqbDrU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792338868; c=relaxed/simple; bh=gVRjbvrRiljqv8ls0gAtpMAJZhAO7VtDAl8BbAqLZbU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=JKRFjZ7vdHLy1EOImI9fQVxoaONPjNvOzB56ElICPQXLTEks46CwQKmjnfo0NSenofNLwsQzKH4DUQyB2f+HJtqkVhP0vpfJLjbupVGaZdOjDW8u8UXY4ss70pjWLFsqE9x1xmYMDcxsyVM9DiGNrjAwlNWSIXFQMJkJhQ18Itc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=eKqjR37p; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="eKqjR37p" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6EE421F000C4; Sun, 18 Oct 2026 15:54:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792338866; bh=7xg5vmAzZnCfRslRIKdO8fNfle/vZg+s00vPo6XgxME=; h=From:To:Cc:Subject:Date:Reply-To; b=eKqjR37pz50YSHkj7ZDPRrORPsS+JWnjnbjbkiW2DkHzkw37gBFINvBKTp3Kv2miI RJHugHfQsSyJUWFfl6l3wg2RibBtcuTIcKBOic+ytsnjb/fic0kYjubin0pl06FfyU 3TPGm5AruCO1wobk9en3WBZlZLdMIiT4Y1BSClpw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98705: wifi: mac80211: account proxy paths against the mesh path limit Date: Sun, 18 Oct 2026 17:44:40 +0200 Message-ID: <2026101806-CVE-2026-98705-1cdd@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2979; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=zmj3wr8SgsJrhH2sSORisB6vNA3xbNvFakxvcjSpAh8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXXro93KwhWTD7e6T45SeSfQbsgS9VlS8I/r7M++RT3 u3ydbuud8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE0rMY5idEHEo+suS2AHt+ VsTZiFstxt//hTEs6GDcvrxhP0PCui9V6TZ/7jQqvNr5BAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-98705 to this issue. Affected and fixed versions =========================== Issue introduced in 3.2 with commit ece1a2e7e86078c8379937b546e32cb7f25fcb6c and fixed in 6.12.113 with commit df072db65fdaa34ad15e1d66fc06a53e3e97f778 Issue introduced in 3.2 with commit ece1a2e7e86078c8379937b546e32cb7f25fcb6c and fixed in 6.18.56 with commit 3b75831ceee76d32bb8e7ddd241904f92f9b5407 Issue introduced in 3.2 with commit ece1a2e7e86078c8379937b546e32cb7f25fcb6c and fixed in 7.2.10 with commit 5a32409ed34a1868830899a5d2437f0b3bf3532c Issue introduced in 3.2 with commit ece1a2e7e86078c8379937b546e32cb7f25fcb6c and fixed in 7.3-rc6 with commit a5f35d4b112af1415ff06bd501c8cc26cc08aa8b Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-98705 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/mac80211/mesh_pathtbl.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/df072db65fdaa34ad15e1d66fc06a53e3e97f778 https://git.kernel.org/stable/c/3b75831ceee76d32bb8e7ddd241904f92f9b5407 https://git.kernel.org/stable/c/5a32409ed34a1868830899a5d2437f0b3bf3532c https://git.kernel.org/stable/c/a5f35d4b112af1415ff06bd501c8cc26cc08aa8b