CVE-2025-38644: wifi: mac80211: reject TDLS operations when station is not associated
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: reject TDLS operations when station is not associated
syzbot triggered a WARN in ieee80211_tdls_oper() by sending
NL80211_TDLS_ENABLE_LINK immediately after NL80211_CMD_CONNECT,
before association completed and without prior TDLS setup.
This left internal state like sdata->u.mgd.tdls_peer uninitialized,
leading to a WARN_ON() in code paths that assumed it was valid.
Reject the operation early if not in station mode or not associated.
Security readout for executives and security teams
Plain-English summary
CVE-2025-38644 is a Linux kernel WiFi bug where a TDLS operation can be accepted before a station is fully associated. The documented result is a kernel WARN caused by invalid internal state assumptions. The sources do not provide CVSS, confirmed exploitation, or broader impact details.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency from the provided evidence. Prioritize patching wireless-capable Linux endpoints and appliances, especially where kernel updates are already operationally scheduled.
Technical view
In mac80211, ieee80211_tdls_oper() could process NL80211_TDLS_ENABLE_LINK after NL80211_CMD_CONNECT but before association and TDLS setup. Internal state such as sdata->u.mgd.tdls_peer could remain uninitialized, reaching a WARN_ON(). The fix rejects TDLS operations unless the interface is station mode and associated.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel builds with WiFi/mac80211 station functionality. The source lists Linux kernel versions and stable commits but does not define privilege requirements, reachable configurations, or whether typical server workloads are exposed.
Exploitation context
The issue was reported through syzbot testing. KEV status is false in the supplied bundle, and no cited source states active exploitation. The bundle does not establish practical exploitation beyond triggering the described WARN path.
Researcher notes
The public record identifies a state-validation flaw in TDLS handling, fixed by early rejection when not in station mode or not associated. Missing data includes CVSS, CWE, privilege requirements, denial-of-service impact, and real-world exploit evidence.
Mitigation direction
Apply Linux kernel or distribution updates containing the referenced stable fixes.
For Debian LTS systems, review the cited Debian LTS advisory.
Prioritize systems with WiFi/mac80211 enabled or client-mode wireless use.
If no update exists, check vendor guidance before applying compensating controls.
Validation and detection
Inventory Linux kernel versions across wireless-capable assets.
Confirm vendor kernels include one of the referenced stable fixes or backports.
Check whether WiFi/mac80211 station mode is enabled on exposed systems.
Track distro advisories for package-level fixed versions and rollout status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38644 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 22, 2025, 16:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.