Skip to content
Fencer Vulns
no cvss —

CVE-2022-50633 json

usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init

published 2025-12-09 11 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55723

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init

of_icc_get() alloc resources for path handle, we should release it when not need anymore. Like the release in dwc3_qcom_interconnect_exit() function. Add icc_put() in error handling to fix this.

Patch / fix

  • Linux Linux 5.10.163, 5.15.87, 6.0.17, 6.1.2, 6.2
  • linux Debian 14, Debian 13, Debian 12 6.1.4-1

debian advisories DEBIAN-CVE-2022-50633

  • linux Ubuntu 22.04 LTS 5.15.0-69.76
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1030.35
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1027.30
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1030.35
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1035.42
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1017.22

ubuntu advisories UBUNTU-CVE-2022-50633

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel RHEL 9 5.14.0-362.8.1.el9_3
  • rv RHEL 9 5.14.0-362.8.1.el9_3
  • perf RHEL 9 5.14.0-362.8.1.el9_3
  • rtla RHEL 9 5.14.0-362.8.1.el9_3
  • bpftool RHEL 9 7.2.0-362.8.1.el9_3
  • libperf RHEL 9 5.14.0-362.8.1.el9_3
  • kernel-rt RHEL 9 5.14.0-362.8.1.el9_3
  • kernel-64k RHEL 9 5.14.0-362.8.1.el9_3

red hat advisories RHSA-2023:6583

  • kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
  • kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
  • kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
  • kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
  • kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
  • kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
  • kernel-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1
  • kernel-source-rt SLE Micro 5.4, SLE Micro 5.3 5.14.21-150400.15.142.1

suse advisories SUSE-SU-2026:0617-1SUSE-SU-2026:0411-1SUSE-SU-2026:0317-1SUSE-SU-2026:0263-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-50633 updated cvss 5.5

kernel: usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.