LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50169: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi()

In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi() The simple_write_to_buffer() function will succeed if even a single byte is initialized. However, we need to initialize the whole buffer to prevent information leaks. Just use memdup_user().

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel information-leak fix in the wil6210 Wi-Fi driver debugfs WMI write path. The flaw could expose uninitialized kernel memory because a partially initialized buffer was accepted. Business urgency is mainly for systems using this driver and affected kernels; no active exploitation is cited.

Executive priority

Treat as routine kernel hygiene unless the environment uses wil6210 hardware or exposes debugfs to less trusted users. Prioritize through normal patch cycles, with faster action for shared, research, or appliance-like systems.

Technical view

wil_write_file_wmi() used simple_write_to_buffer(), which can succeed after only one initialized byte. The kernel fix changes handling to initialize or duplicate the full user buffer with memdup_user(), preventing unintended memory disclosure through the debugfs path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the wil6210 driver and relevant debugfs interface present. Exact exposure depends on kernel build, hardware, driver loading, and debugfs access controls, which are not detailed in the sources.

Exploitation context

The bundle marks CISA KEV as false and provides no public evidence of active exploitation. The sources describe an information leak, not privilege escalation or remote code execution. Practical exploitability cannot be confirmed from the provided evidence.

Researcher notes

The source evidence is narrow: a kernel commit message and CVE metadata. There is no CVSS, CWE, access-vector detail, or exploit report in the bundle. Avoid broader claims without vendor or distribution advisories.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Use distribution advisories to map fixed kernel packages accurately.
  • Review whether wil6210 support is needed on exposed systems.
  • Follow vendor guidance if kernel updates are unavailable.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Check whether wil6210 is built, loaded, or packaged.
  • Confirm systems run a kernel containing the stable fix commit.
  • Verify debugfs exposure and access policy on relevant hosts.
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-50169 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.