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 32FD0371899 for ; Sun, 18 Oct 2026 16:04:21 +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=1792339462; cv=none; b=Loyxuz7Lw+r26usXWXiNtBtpg6r2SRJ+IBSPtxAWyv78QXLqt7K3m185yX9TxzdPRv1cGIM3pTiq4E2eQDn3X5XzU0CT+8FfPJoVmoG0CKxQwSLBJE+bNt2eafEGeschTPEqRIpl4/lqEs3skLlqII1rSiM2aHGFGvEUVceEKYY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792339462; c=relaxed/simple; bh=0Xot81G3d0/+ZGz3v2JxRKCaPpw2pWsS7W1OQjUjPnw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=gOBTvSGlaoewQufuwU1tziABZHtc1Wh2nIvgRamaUdA0tp6ChA67brqTtLRbBrTkfQqKTMqR5fDwCYOPxhA0n5qJuUp3kB+kH69DQje2/an9MJtXJE+DtFcvsLbCtdYSHbjj9mwINygqJlbkqNuNK75FXUQKMlpsV/t4Z0VgFSc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ytrZaq6a; 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="ytrZaq6a" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A4741F000C4; Sun, 18 Oct 2026 16:04:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792339461; bh=rGh+DmKg1kzjZhEeAuGmWkW7ia3hFib2bMkdCp+8yNM=; h=From:To:Cc:Subject:Date:Reply-To; b=ytrZaq6a08TSiADWZ/WhMii5apLPBIeNtZtkS2NG9Cj5P2xTadxG8o7f6Ngiokniv UwCRIPxee9DyljC8j+54oiZOct6WOwaDpzm3gg3Zx9Efbm2oewdpUt9vsozAA9qAaq VMlHavCHnvKqLa4xSqbdf5rdX+Hvpi1EfdihkYgM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98708: wifi: mac80211: keep paired old chanctx alive Date: Sun, 18 Oct 2026 17:44:43 +0200 Message-ID: <2026101806-CVE-2026-98708-aae4@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=3142; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=k7dTPzzp1wDDUovv+IQzDVrhoruYcVFWOBF2GptnFjA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlXXrrFZfYKbXhz9Ejds5cH3925ENGZr825yft03ZJ3r x87sHvGdsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEjl9mWDDRjvGocUfOIk9z kck7GuUus3QqNTMsOMa8wCT8GOPEIyoiCXuYFXM+fg/iAgA= 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: keep paired old chanctx alive An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx. That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer. Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain. The Linux kernel CVE team has assigned CVE-2026-98708 to this issue. Affected and fixed versions =========================== Issue introduced in 3.17 with commit 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and fixed in 6.12.113 with commit 21a688cbeae0e682f03e91f1e7a7eedd60d9d4f2 Issue introduced in 3.17 with commit 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and fixed in 6.18.56 with commit 1c82d0c5d509179ba2a4edfa096f516aebf960b0 Issue introduced in 3.17 with commit 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and fixed in 7.2.10 with commit afd1cdd16a25c7185b812a612ab7d5f2cbd1e086 Issue introduced in 3.17 with commit 5bcae31d9cb1ebfad3ad5a3eea04c8cdc329a04f and fixed in 7.3-rc6 with commit 3412e9a800786d1dec4a58367db1cba275e7ef11 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-98708 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/chan.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/21a688cbeae0e682f03e91f1e7a7eedd60d9d4f2 https://git.kernel.org/stable/c/1c82d0c5d509179ba2a4edfa096f516aebf960b0 https://git.kernel.org/stable/c/afd1cdd16a25c7185b812a612ab7d5f2cbd1e086 https://git.kernel.org/stable/c/3412e9a800786d1dec4a58367db1cba275e7ef11