| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025091548-CVE-2022-50246-d173@gregkh> Date: Mon, 15 Sep 2025 16:01:54 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50246: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@...tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak. The Linux kernel CVE team has assigned CVE-2022-50246 to this issue. Affected and fixed versions =========================== Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 5.4.229 with commit 4f257e2eba419ab4cd880c822346450e4e7b2af3 Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 5.10.163 with commit d3b6c28a71f111a6c67ddc3238aab95910fd86cf Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 5.15.86 with commit ba75be6f0d9d028d20852564206565a4c03e3288 Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 6.0.16 with commit e75a324409715bd71348f79a49aa61b69dbeb676 Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 6.1.2 with commit 5f125507d2270035dfcf83fbff6cff5a143e200c Issue introduced in 4.19 with commit 5e85a04c8c0d271d7561a770b85741f186398868 and fixed in 6.2 with commit 0384e87e3fec735e47f1c133c796f32ef7a72a9b 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-50246 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/tcpm/tcpci.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/4f257e2eba419ab4cd880c822346450e4e7b2af3 https://git.kernel.org/stable/c/d3b6c28a71f111a6c67ddc3238aab95910fd86cf https://git.kernel.org/stable/c/ba75be6f0d9d028d20852564206565a4c03e3288 https://git.kernel.org/stable/c/e75a324409715bd71348f79a49aa61b69dbeb676 https://git.kernel.org/stable/c/5f125507d2270035dfcf83fbff6cff5a143e200c https://git.kernel.org/stable/c/0384e87e3fec735e47f1c133c796f32ef7a72a9b
Powered by blists - more mailing lists