Skip to content
Threat Brief

← All advisories

CVE-2026-99771

Severity unknownNo known exploitationFix available

wifi: mac80211: reload TDLS header pointer after skb_linearize()

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 before 16e23c766ecd9f378e09d29ac2ff59c88a656da516e23c766ecd9f378e09d29ac2ff59c88a656da5CVE Program
LinuxLinuxfrom 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 before 5251ad1a6caa35e6d8378aadb909d3f0a675f3215251ad1a6caa35e6d8378aadb909d3f0a675f321CVE Program
LinuxLinuxfrom 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 before 35c5a5ea4418571997a7e7af3e7e8922b136f6e635c5a5ea4418571997a7e7af3e7e8922b136f6e6CVE Program
LinuxLinuxfrom 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 before 25af938d604fa729e0d5292b4f56bc81aa8d0d2525af938d604fa729e0d5292b4f56bc81aa8d0d25CVE Program
LinuxLinux3.19Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 3.19Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references