CVE-2021-47194: cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
In the Linux kernel, the following vulnerability has been resolved:
cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
If the userspace tools switch from NL80211_IFTYPE_P2P_GO to
NL80211_IFTYPE_ADHOC via send_msg(NL80211_CMD_SET_INTERFACE), it
does not call the cleanup cfg80211_stop_ap(), this leads to the
initialization of in-use data. For example, this path re-init the
sdata->assigned_chanctx_list while it is still an element of
assigned_vifs list, and makes that linked list corrupt.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47194 is a Linux kernel Wi-Fi subsystem bug. A specific interface type change can skip cleanup, leaving internal wireless data structures in an inconsistent state. The public record does not provide CVSS, confirmed real-world exploitation, or a clear business impact, so urgency depends on wireless exposure and vendor kernel status.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless wireless-enabled Linux assets are high value or exposed to untrusted local users. The lack of CVSS and exploitation evidence lowers confidence in urgency.
Technical view
The issue is in cfg80211 when userspace changes an interface from NL80211_IFTYPE_P2P_GO to NL80211_IFTYPE_ADHOC. Missing cfg80211_stop_ap cleanup can reinitialize in-use structures, corrupting a linked list involving sdata->assigned_chanctx_list and assigned_vifs. Stable kernel commits are referenced as the resolution.
Likely exposure
Exposure appears limited to Linux systems using affected kernel builds with wireless cfg80211 functionality and relevant P2P/adhoc interface transitions. Servers without Wi-Fi hardware or disabled wireless paths are less likely to be reachable, but vendor kernel backports must be checked.
Exploitation context
The provided sources do not show CISA KEV listing, public exploitation, exploit code, or attacker prerequisites. The bug requires a userspace-triggered wireless interface type change, but the sources do not define required privileges or impact beyond linked-list corruption.
Researcher notes
The record identifies root cause and stable commit references but omits CVSS, CWE, exploitability conditions, privilege requirements, and final impact class. Validate through kernel source/backport review and distro advisories before assigning operational severity.
Mitigation direction
Check Linux distribution advisories for CVE-2021-47194 coverage.
Update affected kernels to builds containing the referenced stable fixes.
Prioritize laptops, embedded Linux, and wireless-enabled appliances.
Disable unused Wi-Fi/P2P functionality where operationally feasible.
Track vendor backports instead of relying only on upstream version numbers.
Validation and detection
Inventory Linux kernel versions across wireless-capable assets.
Confirm whether cfg80211/mac80211 wireless functionality is enabled.
Map vendor kernel packages to the referenced upstream stable commits.
Verify fixed kernel deployment through normal asset and patch records.
Document exceptions for systems without Wi-Fi exposure.
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-2021-47194 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.