From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
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 [thread overview]
Message-ID: <2026112027-CVE-2026-99768-e56b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-11-20 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112027-CVE-2026-99768-e56b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.