CVE-2022-49881: wifi: cfg80211: fix memory leak in query_regdb_file()
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: fix memory leak in query_regdb_file()
In the function query_regdb_file() the alpha2 parameter is duplicated
using kmemdup() and subsequently freed in regdb_fw_cb(). However,
request_firmware_nowait() can fail without calling regdb_fw_cb() and
thus leak memory.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi subsystem memory leak. A local low-privileged user could potentially cause repeated failed firmware lookups that leak kernel memory, creating availability risk. It does not indicate data theft or remote compromise in the provided sources.
Executive priority
Treat as a moderate availability issue. It is not remote code execution, but shared Linux endpoints or appliances with local user access should be patched through normal kernel maintenance cycles.
Technical view
In cfg80211 query_regdb_file(), alpha2 is duplicated with kmemdup() and normally freed in regdb_fw_cb(). If request_firmware_nowait() fails before invoking that callback, the allocation is not freed, producing a CWE-401 memory leak with availability impact.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel versions with cfg80211 Wi-Fi regulatory database handling. Downstream distribution kernels may differ, so validate against vendor backports and the listed upstream stable commits.
Exploitation context
The provided CVSS vector is local, low complexity, low privileges, no user interaction, availability-only. The source bundle marks KEV as false and provides no evidence of active exploitation or public weaponization.
Researcher notes
Evidence is limited to the CVE description, CVSS data, and kernel stable references. The exact vulnerable version ranges and downstream package status require vendor-specific verification before declaring exposure.
Mitigation direction
Upgrade to a kernel containing the referenced upstream stable fix commits.
Check distribution security advisories for backported fixes matching CVE-2022-49881.
Prioritize systems where untrusted local users can run code.
Monitor affected systems for memory pressure until patched.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and appliances.
Map each kernel to vendor advisories or the referenced stable commits.
Identify systems using Wi-Fi/cfg80211 functionality where local users have access.
Confirm patch deployment through package metadata or kernel build provenance.
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-401: 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.
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-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.