LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49934: wifi: mac80211: Fix UAF in ieee80211_scan_rx()

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Fix UAF in ieee80211_scan_rx() ieee80211_scan_rx() tries to access scan_req->flags after a null check, but a UAF is observed when the scan is completed and __ieee80211_scan_completed() executes, which then calls cfg80211_scan_done() leading to the freeing of scan_req. Since scan_req is rcu_dereference()'d, prevent the racing in __ieee80211_scan_completed() by ensuring that from mac80211's POV it is no longer accessed from an RCU read critical section before we call cfg80211_scan_done().

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49934 is a Linux kernel Wi-Fi bug in mac80211. A scan request can be freed while another path still reads it, creating a use-after-free condition. The public record does not state impact, CVSS, or active exploitation, so urgency depends on whether affected wireless-capable Linux kernels are in use.

Executive priority

Handle through normal kernel patch governance unless your environment heavily depends on Wi-Fi-enabled Linux endpoints or embedded devices. Lack of CVSS and KEV evidence prevents a stronger emergency rating, but kernel memory safety bugs should not be ignored.

Technical view

The issue is in ieee80211_scan_rx(). scan_req is obtained through RCU, but scan completion can call cfg80211_scan_done(), freeing scan_req while ieee80211_scan_rx() still accesses scan_req->flags. Kernel stable commits change completion handling so mac80211 no longer accesses the request from an RCU read critical section before cfg80211_scan_done().

Likely exposure

Exposure is most relevant to Linux systems using mac80211 Wi-Fi functionality on affected kernel versions. The source lists Linux as affected and references multiple stable kernel fixes. Servers without Wi-Fi hardware or unused wireless scanning are less likely to be exposed, but kernel inventory is required.

Exploitation context

The provided sources do not report exploitation in the wild, and this CVE is not marked KEV. They also do not describe attacker prerequisites, exploitability, or real-world impact. Treat exploitation status as unknown, not actively exploited.

Researcher notes

Evidence is limited to the CVE description and kernel stable references. The record identifies a race-driven UAF around scan_req lifetime, but does not provide impact, privilege boundary, trigger conditions, or affected distribution packages. Validate against upstream commits and downstream vendor backports.

Mitigation direction

  • Identify Linux systems with Wi-Fi/mac80211 support enabled or deployed.
  • Update affected kernels to vendor-supported builds containing the referenced stable fixes.
  • Prioritize laptops, workstations, gateways, and embedded devices using wireless scanning.
  • Check distribution advisories for exact fixed package versions.
  • Avoid ad hoc kernel patching outside vendor-supported maintenance processes.

Validation and detection

  • Inventory kernel versions across Linux endpoints and appliances.
  • Confirm whether mac80211 Wi-Fi functionality is present and used.
  • Map installed kernels against vendor advisories and stable fix commits.
  • Verify patched systems are running the updated kernel after reboot.
  • Review vulnerability scanner findings for CVE-2022-49934 coverage gaps.
Prepared
Confidence
medium
Sources
10

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-49934 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
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749, 6ea0a69ca21bbddab5b3979c2190013b0263e749unaffected
LinuxLinux3.19, 0, 4.9.330, 4.14.295, 4.19.260, 5.4.215, 5.10.142, 5.15.66, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

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