LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47225: mac80211: fix deadlock in AP/VLAN handling

In the Linux kernel, the following vulnerability has been resolved: mac80211: fix deadlock in AP/VLAN handling Syzbot reports that when you have AP_VLAN interfaces that are up and close the AP interface they belong to, we get a deadlock. No surprise - since we dev_close() them with the wiphy mutex held, which goes back into the netdev notifier in cfg80211 and tries to acquire the wiphy mutex there. To fix this, we need to do two things: 1) prevent changing iftype while AP_VLANs are up, we can't easily fix this case since cfg80211 already calls us with the wiphy mutex held, but change_interface() is relatively rare in drivers anyway, so changing iftype isn't used much (and userspace has to fall back to down/change/up anyway) 2) pull the dev_close() loop over VLANs out of the wiphy mutex section in the normal stop case

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-47225 is a Linux kernel availability bug in Wi-Fi AP/VLAN handling. A local, low-privileged user could trigger a deadlock when AP_VLAN interfaces are active and the parent AP interface is closed. The known impact is service disruption, not data theft or remote code execution.

Executive priority

Treat as a moderate availability risk. It is not presented as remote compromise or data exposure, but affected Linux wireless AP deployments could hang under the described conditions. Patch through normal kernel maintenance, accelerating for systems where Wi-Fi AP availability is business-critical.

Technical view

The mac80211 AP/VLAN stop path called dev_close() while holding the wiphy mutex. That re-entered cfg80211 netdev notifier logic and attempted to acquire the same mutex, causing a deadlock. The fix prevents interface type changes while AP_VLANs are up and moves VLAN dev_close() outside the locked section.

Likely exposure

Exposure appears limited to Linux systems using affected kernels and mac80211 wireless AP/AP_VLAN configurations. Generic servers without Wi-Fi AP/VLAN use are less likely to be exposed. The bundle identifies Linux kernel versions around 5.12 through 5.13 and related stable commits, but distribution-specific backport status must be verified.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. CVSS rates this as local, low-complexity, low-privilege, no-user-interaction, availability-only impact. The issue was reported by syzbot, suggesting automated kernel testing found the deadlock rather than a public exploitation campaign.

Researcher notes

Evidence is strongest for root cause and kernel fix direction from the CVE description and Linux stable references. The bundle does not provide exploit proof, affected distribution mapping, or operational telemetry. Validation should focus on kernel provenance and AP_VLAN usage rather than broad Linux fleet assumptions.

Mitigation direction

  • Apply vendor kernel updates that include the linked Linux stable fixes.
  • Prioritize systems using mac80211 AP mode with AP_VLAN interfaces.
  • Verify distribution backports before assuming version numbers are vulnerable or fixed.
  • Restrict local privileges for network interface management until patched.
  • Check vendor guidance if patching must be delayed.

Validation and detection

  • Inventory Linux kernel versions on Wi-Fi AP-capable systems.
  • Identify hosts using mac80211 AP mode or AP_VLAN interfaces.
  • Confirm patched kernels include the referenced stable commits or vendor backports.
  • Review vendor advisories for distribution-specific affected and fixed versions.
  • Check for availability incidents during AP/VLAN interface teardown.
Prepared
Confidence
high
Sources
4

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-47225 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-47225Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa05829a7222e9d10c416dd2dbbf3929fe6646b89, a05829a7222e9d10c416dd2dbbf3929fe6646b89unaffected
LinuxLinux5.12, 0, 5.12.13, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.