CVE-2025-21979: wifi: cfg80211: cancel wiphy_work before freeing wiphy
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: cancel wiphy_work before freeing wiphy
A wiphy_work can be queued from the moment the wiphy is allocated and
initialized (i.e. wiphy_new_nm). When a wiphy_work is queued, the
rdev::wiphy_work is getting queued.
If wiphy_free is called before the rdev::wiphy_work had a chance to run,
the wiphy memory will be freed, and then when it eventally gets to run
it'll use invalid memory.
Fix this by canceling the work before freeing the wiphy.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi stack memory safety flaw. A local low-privileged user may be able to trigger use of freed kernel memory, with potential impact to confidentiality, integrity, and availability. The issue is serious on systems running affected kernels, but the supplied sources do not show active exploitation.
Executive priority
Prioritize normal-to-expedited kernel patching for Linux fleets, especially endpoints and wireless-capable systems. This is high severity because kernel memory corruption can have broad system impact, but urgency is below emergency level without evidence of active exploitation.
Technical view
In cfg80211, wiphy_work can remain queued after wiphy_free releases the associated wiphy memory. When the queued work later runs, it may dereference invalid memory, producing a CWE-416 use-after-free. The kernel fix cancels pending wiphy_work before freeing the wiphy object.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel versions and the cfg80211 wireless stack. The source bundle lists Linux kernel affected ranges including 6.5 and stable series entries through 6.14. Downstream distribution exposure depends on vendor backports and package status.
Exploitation context
The CVSS vector is local, low complexity, low privilege, and no user interaction. The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. Treat exploitability as plausible local privilege-impact risk, not confirmed active exploitation.
Researcher notes
The key evidence is the upstream fix description: queued rdev::wiphy_work could execute after wiphy memory is freed. Validate exposure through kernel version, downstream patch status, and wireless stack presence. The affected-version data in the bundle is not enough to infer every vendor package state.
Mitigation direction
Apply Linux kernel or distribution security updates containing the cfg80211 wiphy_work fix.
Review Debian LTS and other vendor advisories for patched kernel package availability.
Prioritize laptops, workstations, and systems with wireless stack support enabled.
Where patching is delayed, follow vendor guidance for temporary risk reduction.
Reboot into the patched kernel after updating kernel packages.
Validation and detection
Inventory running kernel versions across Linux assets.
Check whether each distribution has backported the referenced kernel fix.
Confirm systems have rebooted into the patched kernel after update.
Identify assets with cfg80211 or wireless drivers enabled.
Document exceptions where vendor patch status is still unclear.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.