CVE-2022-50357: usb: dwc3: core: fix some leaks in probe
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3: core: fix some leaks in probe
The dwc3_get_properties() function calls:
dwc->usb_psy = power_supply_get_by_name(usb_psy_name);
so there is some additional clean up required on these error paths.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50357 is a Linux kernel resource leak in the USB DWC3 probe path. A local user could potentially trigger conditions that consume kernel memory and reduce system availability. It is not reported as actively exploited, and the published impact is availability only.
Executive priority
Treat as routine-to-priority patching where local users, containers, or untrusted workloads exist. For managed appliances and embedded devices, track vendor firmware updates. This is not currently an emergency remote-exploitation issue based on available sources.
Technical view
The issue is a CWE-401 memory leak in Linux kernel usb/dwc3 core probe error handling. dwc3_get_properties() obtains a power_supply reference, and some error paths lacked cleanup. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the DWC3 USB controller driver path in use. This commonly matters more for embedded, mobile, appliance, and SoC-based Linux platforms than generic servers, but validation must be environment-specific.
Exploitation context
Sources do not show KEV listing or active exploitation. The CVSS vector requires local privileges and indicates no confidentiality or integrity impact. Practical risk centers on local denial of service through resource exhaustion, not remote compromise.
Researcher notes
The public record identifies cleanup fixes around power_supply_get_by_name() references in dwc3 probe error paths. Affected version data in the source bundle is limited and somewhat coarse; use kernel stable commits and downstream vendor backports for precise exposure decisions.
Mitigation direction
Review Linux distribution or device vendor advisories for this CVE.
Update to a kernel build containing the referenced stable fixes.
Prioritize internet-facing appliances only if local user access is plausible.
For embedded devices, request firmware status from the device vendor.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded products.
Identify systems using the Linux USB DWC3 driver path.
Compare deployed kernels with vendor advisories and referenced stable commits.
Confirm remediation through vendor package or firmware release notes.
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.