[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123017-CVE-2022-50825-905f@gregkh>
Date: Tue, 30 Dec 2025 13:09:29 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50825: usb: typec: wusb3801: fix fwnode refcount leak in wusb3801_probe()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: wusb3801: fix fwnode refcount leak in wusb3801_probe()
I got the following report while doing fault injection test:
OF: ERROR: memory leak, expected refcount 1 instead of 4,
of_node_get()/of_node_put() unbalanced - destroy cset entry:
attach overlay node /i2c/tcpc@...connector
If wusb3801_hw_init() fails, fwnode_handle_put() needs be called to
avoid refcount leak.
The Linux kernel CVE team has assigned CVE-2022-50825 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit d016cbe4d7acf5100df83ecf4d02db4e9f607c1d and fixed in 6.0.16 with commit de1e2eb7f102e3073714396414592a39efb66b3e
Issue introduced in 5.18 with commit d016cbe4d7acf5100df83ecf4d02db4e9f607c1d and fixed in 6.1.2 with commit 82d1211f673bbdc822eaf1dbcbf1f2ae06556964
Issue introduced in 5.18 with commit d016cbe4d7acf5100df83ecf4d02db4e9f607c1d and fixed in 6.2 with commit dc18a4c7b3bd447cef2395deeb1f6ac16dfaca0e
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-50825
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/typec/wusb3801.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/de1e2eb7f102e3073714396414592a39efb66b3e
https://git.kernel.org/stable/c/82d1211f673bbdc822eaf1dbcbf1f2ae06556964
https://git.kernel.org/stable/c/dc18a4c7b3bd447cef2395deeb1f6ac16dfaca0e
Powered by blists - more mailing lists