LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48784: cfg80211: fix race in netlink owner interface destruction

In the Linux kernel, the following vulnerability has been resolved: cfg80211: fix race in netlink owner interface destruction My previous fix here to fix the deadlock left a race where the exact same deadlock (see the original commit referenced below) can still happen if cfg80211_destroy_ifaces() already runs while nl80211_netlink_notify() is still marking some interfaces as nl_owner_dead. The race happens because we have two loops here - first we dev_close() all the netdevs, and then we destroy them. If we also have two netdevs (first one need only be a wdev though) then we can find one during the first iteration, close it, and go to the second iteration -- but then find two, and try to destroy also the one we didn't close yet. Fix this by only iterating once.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel wireless networking bug in cfg80211. A race during netlink-owned wireless interface cleanup can recreate a deadlock the earlier fix tried to prevent. The public record does not provide CVSS, active exploitation, or clear business-impact details beyond the deadlock condition.

Executive priority

Treat this as a kernel maintenance and availability-risk item, not a confirmed emergency. Prioritize wireless-capable Linux fleets and internet-scale operations that depend on uptime, while waiting for vendor severity and backport confirmation.

Technical view

CVE-2022-48784 affects Linux cfg80211/nl80211 interface destruction. Concurrent nl80211_netlink_notify() marking interfaces as owner-dead and cfg80211_destroy_ifaces() closing then destroying interfaces can destroy an interface before it was closed. The fix changes the logic to iterate once.

Likely exposure

Exposure is most relevant to Linux systems using the kernel wireless cfg80211/nl80211 stack on affected kernel versions listed in the CVE record, including 5.13, 5.15.25, 5.16.11, and 5.17. Distro backports may change practical exposure.

Exploitation context

The supplied sources do not state active exploitation, exploit availability, attacker location, required privileges, or reliable trigger conditions. CISA KEV status is false in the bundle, so active exploitation should not be assumed.

Researcher notes

The record describes a race and deadlock avoidance fix, but does not provide CVSS, CWE, trigger requirements, or exploitability details. Research should focus on kernel version lineage, distro backports, and whether affected deployments expose nl80211 workflows.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-48784 guidance.
  • Update to a vendor-supported kernel containing the stable cfg80211 fix.
  • Prioritize systems with wireless networking enabled or managed dynamically.
  • Track kernel versions separately from distribution package versions.
  • Avoid claiming remediation complete until vendor backport status is confirmed.

Validation and detection

  • Inventory Linux hosts and running kernel versions.
  • Identify systems using wireless cfg80211/nl80211 functionality.
  • Compare installed kernels against vendor CVE-2022-48784 advisories.
  • Confirm fixed kernel packages include the cited stable commits.
  • Review change management records for kernel updates after July 16, 2024.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2022-48784 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxea6b2098dd02789f68770fd3d5a373732207be2f, ea6b2098dd02789f68770fd3d5a373732207be2f, ea6b2098dd02789f68770fd3d5a373732207be2f, 2e4f97122f3a9df870dfe9671994136448890768, 5.12.1unaffected
LinuxLinux5.13, 0, 5.15.25, 5.16.11, 5.17affected
Weakness

CWE details

No CWE listed

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