wifi: mac80211: reload TDLS header pointer after skb_linearize()
Summary
| CVE | CVE-2026-99771 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:15 UTC |
| Updated | 2026-11-20 06:18:15 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: reload TDLS header pointer after skb_linearize()
ieee80211_process_tdls_channel_switch() sets tf = skb->data before it
calls skb_linearize(), and reads tf->action_code afterwards.
ieee80211_rx_h_data() queues TDLS channel switch requests and
responses to the interface after pulling only
offsetof(struct ieee80211_tdls_data, u) bytes, so the skb can still be
non-linear when the interface work handles it. Drivers that build
paged RX skbs do this for every frame that does not fit into the skb
head, e.g. iwlwifi (mvm), which is also the only mac80211 driver
that sets NL80211_FEATURE_TDLS_CHANNEL_SWITCH. If the remaining data
does not fit into the tailroom, skb_linearize() moves the data to a
new head and frees the old one, and the action code is then read from
freed memory. Depending on what that memory holds by then, the frame
is handled as before or ends in the WARN_ON_ONCE() of the default
case.
The frame only has to be a data frame with the TDLS ethertype from an
authorized peer, e.g. relayed by the AP from another station in the
BSS; the read happens before the sender is checked to be a TDLS peer.
Load tf after skb_linearize(), as the request and response handlers
already do.
Found by static analysis tool CodeQL. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 25af938d604fa729e0d5292b4f56bc81aa8d0d25 git |
Not specified |
| CNA |
Linux |
Linux |
affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 16e23c766ecd9f378e09d29ac2ff59c88a656da5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 5251ad1a6caa35e6d8378aadb909d3f0a675f321 git |
Not specified |
| CNA |
Linux |
Linux |
affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 35c5a5ea4418571997a7e7af3e7e8922b136f6e6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.19 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.19 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.118 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/16e23c766ecd9f378e09d29ac2ff59c88a656da5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/35c5a5ea4418571997a7e7af3e7e8922b136f6e6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5251ad1a6caa35e6d8378aadb909d3f0a675f321 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/25af938d604fa729e0d5292b4f56bc81aa8d0d25 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.