From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-50357: usb: dwc3: core: fix some leaks in probe
Date: Wed, 17 Sep 2025 16:56:16 +0200 [thread overview]
Message-ID: <2025091714-CVE-2022-50357-4ae9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2022-50357 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 6f0764b5adea18d70c3fab32d5f940678bcbd865 and fixed in 5.19.17 with commit 79c3afb55942368921237d7b5355d48c52bdde20
Issue introduced in 5.13 with commit 6f0764b5adea18d70c3fab32d5f940678bcbd865 and fixed in 6.0.3 with commit 3a213503f483173e7eea76f2e7e3bdd6df7fd6f8
Issue introduced in 5.13 with commit 6f0764b5adea18d70c3fab32d5f940678bcbd865 and fixed in 6.1 with commit 2a735e4b5580a2a6bbd6572109b4c4f163c57462
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50357
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/usb/dwc3/core.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/79c3afb55942368921237d7b5355d48c52bdde20
https://git.kernel.org/stable/c/3a213503f483173e7eea76f2e7e3bdd6df7fd6f8
https://git.kernel.org/stable/c/2a735e4b5580a2a6bbd6572109b4c4f163c57462
reply other threads:[~2025-09-17 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025091714-CVE-2022-50357-4ae9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.