From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup
Date: Fri, 28 Aug 2026 08:53:45 +0200 [thread overview]
Message-ID: <2026082811-CVE-2026-80722-9ad4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: validate individual TWT params before driver setup
ieee80211_process_rx_twt_action() only partially validates a received
S1G TWT setup frame before queueing it.
An individual agreement can therefore reach ieee80211_s1g_rx_twt_setup()
with twt->length too short for the full struct ieee80211_twt_params.
The individual path passes twt to drv_add_twt_setup(). Both the tracepoint
and the driver callback consume the complete parameters block, not merely
req_type. Do not pass a short individual agreement to the driver.
Broadcast agreements remain unchanged because they are rejected locally
after accessing only req_type.
[edit commit message to not overclaim lack of validation nor
understate driver impact]
The Linux kernel CVE team has assigned CVE-2026-80722 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 5.15.216 with commit 92fcd0f30dc8e51f252589b082d46851d295cc1a
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 6.1.183 with commit 09d60d1f72e6598241490eb6c4e97245af895c09
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 6.6.151 with commit ff558072d199c1d641d1561da622e67f780514de
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 6.12.103 with commit ade9e2f0f7f4d3089600ac2af8ef0b91746f923b
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 6.18.44 with commit b558e07708d886acfcf4b0391ed7a8546e81d326
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 7.1.8 with commit 47fb04c3826e1f90271d405523043d6708b9072a
Issue introduced in 5.15 with commit f5a4c24e689f54e66201f04d343bdd2e8a1d7923 and fixed in 7.2 with commit 0502d5077e419427d80f4d46ba95d0067f5fb916
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-80722
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/s1g.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/92fcd0f30dc8e51f252589b082d46851d295cc1a
https://git.kernel.org/stable/c/09d60d1f72e6598241490eb6c4e97245af895c09
https://git.kernel.org/stable/c/ff558072d199c1d641d1561da622e67f780514de
https://git.kernel.org/stable/c/ade9e2f0f7f4d3089600ac2af8ef0b91746f923b
https://git.kernel.org/stable/c/b558e07708d886acfcf4b0391ed7a8546e81d326
https://git.kernel.org/stable/c/47fb04c3826e1f90271d405523043d6708b9072a
https://git.kernel.org/stable/c/0502d5077e419427d80f4d46ba95d0067f5fb916
reply other threads:[~2026-08-28 6:55 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=2026082811-CVE-2026-80722-9ad4@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.