From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154506; b=BuEu4mVArA73io73M4RxChXJLIwmUJuZX6Z54W3tVG45Efzgyv95eN/yffLU0t0EXf4w VFgHS5DmoUglcc41Snxnp9uCnTcNMQzMAMAk3blzQ3XNmLx5pLyEELQSTzmJDtSuWR9sC PV0aibqlgcPailc5VyZH5FsZQ/Rtlq2a3k+j3bQyXOR+JaROoEyiCaQ6iyHuHQ/KgE+Kq 5yPfScWm4T9wK16M9HdS4khbJmDYuH8DLRAvauM5RaH0gR+Xrj4exZgJSnt2ZRrqQEj3S moJtncSlAOJinobe0q24uQVo6srgiNth6MyL0ZH+d1WV/cVJHhDQSXV5AOSCRRpPE0Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154506; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=NEoRIXmdwUenMOBU00eN6J6DHv+C8bugjFWjJEy+cIY=; b=0Vb31zM1AV870vKr3M5CPRAr7vRk72tAFzoC7BF/dDNHRfb8NJWno9k4OB4efSrmkbAw paFPWKin/NeO1wwgG9j4uGFbAbjiPzCVv3Ji8plKesRyfSnahucy/bbhdSdO9V2bVeReV 3dWt3FzkArxuzb2BxvjS2dF3dxbEMT1Btow65EwhTZgDvAq/NWs4NyaRZZ0hKLx8/PAsX e4sFYyLiGJdVUbcLb4WPgD98sSXhgKbTTrfP7+B7qLfQJu5X0yoPCyq2rg8ftupId+GDg WkQijKhd6t23KT7syxOkv/37udOr7JKsmbMQf3uDYkYEjOK3bgFRgwweQE8S27Sz5xQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nioa89cn; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 174EA606A336 for ; Fri, 20 Nov 2026 06:01:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nioa89cn Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6447C1F000C6; Fri, 20 Nov 2026 06:01:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154505; bh=NEoRIXmdwUenMOBU00eN6J6DHv+C8bugjFWjJEy+cIY=; h=From:To:Cc:Subject:Date:Reply-To; b=nioa89cnr3t3vVvjAtjVLHQ9jBsO4PG+IJGWgP+5SCzQBtghQDK4OD0iZJhDYCeCy l9wvTlyemw+gLKmVz181+Esmvs6MzgKDkWW3IGrbkU1x4Pwu9vsA1myopiJzxPMUU8 ts6+Wdxsjj1VNIRoI3MAxyqgHV72o+tfVsVOoEto= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99768: wifi: mac80211: reinstate IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg() Date: Fri, 20 Nov 2026 06:52:34 +0100 Message-ID: <2026112027-CVE-2026-99768-e56b@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3153; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=J84zFNWlrcnScKHWv8JKT4sgIAuZyRjNECOTjjN3Gec=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7y+u7NzB9U/JOCSZe/rSzVKzrPOfXalJsmlcFPR28 6SyAzz8HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRd80M8yxeHV1wUt/ny2tR 5RClK3ErnWWm32GYp3jfbpfJgQPLCvJeHDH7fTXmLMP5XgA= 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: reinstate IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg() The commit 592234e941f1 ("wifi: mac80211: Fix iTXQ AMPDU fragmentation handling") changed the way handling of the IEEE80211_TX_CTL_AMPDU flag is done in mac80211, so the only place it is set is in ieee80211_tx_dequeue(). This means that any frames that are sent to the driver via drv_tx() will no longer have the flag set. In particular, this affects packets going through ieee80211_tx_pending(). Evan reported that this can result in the ath9k driver failing to account such packets in its block ack window, eventually overrunning the window and stalling TX. Fix this by reinstating the flag in ieee80211_tx_prep_agg() when inside a valid block ack window. This should be harmless for the TXQ path, and will reinstate the previous behaviour for drivers that use the flag as a signal to track the packet in the window. The Linux kernel CVE team has assigned CVE-2026-99768 to this issue. Affected and fixed versions =========================== Issue introduced in 6.2 with commit 592234e941f1addaa598601c9227e3b72d608625 and fixed in 6.12.118 with commit fb658fe8f26994da161cd75f8e32afdef4ed134e Issue introduced in 6.2 with commit 592234e941f1addaa598601c9227e3b72d608625 and fixed in 6.18.64 with commit fb9bcf4d90538ad30979266aa315fe3c5b9f1942 Issue introduced in 6.2 with commit 592234e941f1addaa598601c9227e3b72d608625 and fixed in 7.3.5 with commit 03a00b6be3cec2e701e05c877cc210f4555d8b2e Issue introduced in 6.2 with commit 592234e941f1addaa598601c9227e3b72d608625 and fixed in 7.4-rc2 with commit 25e73f1d6868c759c8eb56cad4e411692c5341b4 Issue introduced in 6.1.9 with commit 63cccc92768dabe2a1aa09e858d69a16ce9814f9 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-99768 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/tx.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/fb658fe8f26994da161cd75f8e32afdef4ed134e https://git.kernel.org/stable/c/fb9bcf4d90538ad30979266aa315fe3c5b9f1942 https://git.kernel.org/stable/c/03a00b6be3cec2e701e05c877cc210f4555d8b2e https://git.kernel.org/stable/c/25e73f1d6868c759c8eb56cad4e411692c5341b4