LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50165: wifi: wil6210: debugfs: fix uninitialized variable use in `wil_write_file_wmi()`

In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix uninitialized variable use in `wil_write_file_wmi()` Commit 7a4836560a61 changes simple_write_to_buffer() with memdup_user() but it forgets to change the value to be returned that came from simple_write_to_buffer() call. It results in the following warning: warning: variable 'rc' is uninitialized when used here [-Wuninitialized] return rc; ^~ Remove rc variable and just return the passed in length if the memdup_user() succeeds.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel bug in the wil6210 Wi-Fi driver's debugfs handling. The source describes an uninitialized return value after a code change. Public data does not provide CVSS, CWE, or impact details, so business urgency should be tied to affected kernel presence rather than assumed exploitability.

Executive priority

Treat as a kernel maintenance item with uncertain severity. Prioritize confirmation on Linux assets using wil6210 or debugfs, then remediate through normal kernel update channels unless vendor guidance raises urgency.

Technical view

The affected function is wil_write_file_wmi() in the wil6210 debugfs path. A prior change replaced simple_write_to_buffer() with memdup_user() but left an uninitialized rc variable returned on success. The fix removes rc and returns the supplied length when memdup_user() succeeds.

Likely exposure

Likely limited to Linux systems running listed affected kernel branches with the wil6210 driver and relevant debugfs path available. The source does not state remote reachability, required privileges, or practical attack conditions.

Exploitation context

The source bundle says KEV is false and provides no evidence of active exploitation or public weaponization. It also lacks CVSS, CWE, and impact scoring, so exploitation likelihood cannot be reliably rated from these sources alone.

Researcher notes

Evidence supports a code-quality memory/control-flow bug in a debugfs write handler, but not practical impact. Avoid assuming remote exploitation, privilege escalation, or denial of service without additional vendor or kernel maintainer analysis.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for patched kernel package versions.
  • Prioritize systems that use wil6210 hardware or expose debugfs workflows.
  • Limit debugfs availability where operationally unnecessary and vendor-supported.

Validation and detection

  • Inventory Linux kernel versions against the affected version list.
  • Confirm whether wil6210 driver support is present or loaded.
  • Check vendor kernel changelogs for the referenced stable commit fixes.
  • Verify debugfs exposure policy on affected Linux systems.
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-50165 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
LinuxLinuxff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0, ff974e4083341383d3dd4079e52ed30f57f376f0unaffected
LinuxLinux3.17, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 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.