Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99771wifi: mac80211: reload TDLS header pointer after skb_linearize()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 56 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.

EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 – < 25af938d604fa729e0d5292b4f56bc81aa8d0d25
    • affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 – < 16e23c766ecd9f378e09d29ac2ff59c88a656da5
    • affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 – < 5251ad1a6caa35e6d8378aadb909d3f0a675f321
    • affected 8a4d32f30d11d6d8cc29594c7a36b9be6b0edbb5 – < 35c5a5ea4418571997a7e7af3e7e8922b136f6e6
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 6.12.118 – ≤ 6.12.*
    • unaffected 6.18.64 – ≤ 6.18.*
    • unaffected 7.3.5 – ≤ 7.3.*
    • unaffected 7.4-rc2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99771 badge
[![CVE-2026-99771](https://cveledger.app/badge/CVE-2026-99771.svg)](https://cveledger.app/cve/CVE-2026-99771)

Record last updated .