Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21979: wifi: cfg80211: cancel wiphy_work before freeing wiphy

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0272d4af7f92997541d8bbf4c51918b93ded6ee2, 6.1.132, 72d520476a2fab6f3489e8388ab524985d6c4b90; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2.

Low priority for now. Upgrade to Linux Linux 0272d4af7f92997541d8bbf4c51918b93ded6ee2, 6.1.132, 72d520476a2fab6f3489e8388ab524985d6c4b90; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 1, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-21979

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.1.57 and later · before 6.1.132
  • linux linux kernel6.5 and later · before 6.6.84
  • linux linux kernel6.7 and later · before 6.12.20
  • linux linux kernel6.13 and later · before 6.13.8
  • linux linux kernel6.14

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.5affected
    • ddb1bfbf4ab5c753954d0cd728253b642934a9f2 and later · before 8930a3e1568cf534f86c8ed2def817c6d0528fc1affected · git
    • 3fcc6d7d5f40dad56dee7bde787b7e23edd4b93c and later · before 0272d4af7f92997541d8bbf4c51918b93ded6ee2affected · git
    • a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and later · before 75d262ad3c36d52852d764588fcd887f0fcd9138affected · git
    • a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and later · before a5158d67bff06cb6fea31be39aeb319fd908ed8eaffected · git
    • a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and later · before dea22de162058216a90f2706f0d0b36f0ff309fdaffected · git
    • a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and later · before 72d520476a2fab6f3489e8388ab524985d6c4b90affected · git
    • 6.1.57 and later · before 6.1.132affected · semver
    • before 6.5not affected · semver
    • 6.1.132 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21968Apr 1, 2025 · drm/amd/display: Fix slab-use-after-free on hdcp_work
    31Monitor
  • ← EarlierCVE-2025-21977Apr 1, 2025 · fbdev: hyperv_fb: Fix hang in kdump kernel when on Hyper-V Gen 2 VMs
    22Monitor
  • Later →CVE-2025-21980Apr 1, 2025 · sched: address a potential NULL pointer dereference in the GRED scheduler.
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0272d4af7f92997541d8bbf4c51918b93ded6ee2Vendor (CNA)
Linux Linux6.1.132Vendor (CNA)
Linux Linux72d520476a2fab6f3489e8388ab524985d6c4b90Vendor (CNA)
Linux Linux75d262ad3c36d52852d764588fcd887f0fcd9138Vendor (CNA)
Linux Linux8930a3e1568cf534f86c8ed2def817c6d0528fc1Vendor (CNA)
Linux Linuxa5158d67bff06cb6fea31be39aeb319fd908ed8eVendor (CNA)
Linux Linuxdea22de162058216a90f2706f0d0b36f0ff309fdVendor (CNA)
azl3 kernel 6.6.82.1-1 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.17.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records