Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a reference-count leak in a USB Type-C WUSB3801 driver error path. It is hardware- and driver-specific, and the source bundle does not show active exploitation, CVSS, or broad impact details.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless your fleet includes affected USB Type-C hardware and vulnerable kernels.
Technical view
In wusb3801_probe(), if wusb3801_hw_init() fails, the driver failed to release a firmware node handle with fwnode_handle_put(), causing an unbalanced refcount leak. The fix is present in referenced Linux stable commits.
Likely exposure
Likely limited to Linux systems using the WUSB3801 USB Type-C controller driver on affected kernel versions or vendor kernels carrying the vulnerable code.
Exploitation context
No KEV listing and no cited source reports active exploitation. The described trigger is a probe failure path found during fault injection testing, not a documented remote attack path.
Researcher notes
Evidence supports a resource leak in a specific Linux driver error path. Public sources do not provide CVSS, CWE mapping, exploitability assessment, or operational impact beyond the refcount leak report.
Mitigation direction
- Check vendor kernel advisories and apply kernels containing the referenced stable fixes.
- Prioritize systems with WUSB3801 USB Type-C controller hardware or enabled driver support.
- If no vendor patch is available, request backport guidance from the kernel or device vendor.
- Track this as lower urgency unless exposed production devices match the affected driver path.
Validation and detection
- Inventory Linux kernel versions and vendor kernel patch levels.
- Confirm whether the WUSB3801 Type-C driver is built, loaded, or used by target hardware.
- Compare vendor kernel source against the referenced stable commits.
- Review kernel logs for firmware node refcount leak warnings during device probe failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-50825 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/de1e2eb7f102e3073714396414592a39efb66b3eCVE reference, Linux
- https://git.kernel.org/stable/c/82d1211f673bbdc822eaf1dbcbf1f2ae06556964CVE reference, Linux
- https://git.kernel.org/stable/c/dc18a4c7b3bd447cef2395deeb1f6ac16dfaca0eCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.